Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'unionfs'

This is an experimental report containing PRs for tag 'unionfs' as of 4-24-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'unionfs':
SSubmittedTrackerResp.Description
o2013/01/20kern/175449fs[unionfs] unionfs and devfs misbehaviour
o2012/10/27kern/173136fs[unionfs] mounting above the NFS read-only share panic
o2012/10/05kern/172348fs[unionfs] umount -f of filesystem in use with readonly backed filesystem results in panic
o2012/10/04kern/172334fs[unionfs] unionfs permits recursive union mounts; causes panic quickly
o2012/02/13kern/165087fs[unionfs] lock violation in unionfs
o2011/03/29kern/156039fs[nullfs] [unionfs] nullfs + unionfs do not compose, result in unlocking unlocked lock
o2010/04/16kern/145750fs[unionfs] [hang] unionfs locks the machine
o2009/12/24kern/141950fs[unionfs] [lor] ufs/unionfs/ufs Lock order reversal
o2009/08/09kern/137588fs[unionfs] [lor] LOR nfs/ufs/nfs
o2009/02/06kern/131441fs[unionfs] [nullfs] unionfs and/or nullfs not combineable
a2008/10/08bin/127932[unionfs] mkdir -p PATH fails if a directory in PATH is on a read-only unionfs
o2008/08/30kern/126973fs[unionfs] [hang] System hang with unionfs and init chroot [regression]
o2008/08/15kern/126553fs[unionfs] unionfs move directory problem 2 (files appear)
o2008/05/10bin/123574fs[unionfs] df(1) -t option destroys info for unionfs (and maybe other) mounts
o2000/07/08bin/19772[unionfs] df(1) output wrong for union-mounts
15 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.