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

Site Navigation

PRs for tag 'nullfs'

This is an experimental report containing PRs for tag 'nullfs' as of 4-16-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 'nullfs':
SSubmittedTrackerResp.Description
p2013/07/03kern/180236fs[zfs] [nullfs] Leakage free space using ZFS with nullfs on 9.1-STABLE
o2013/04/29kern/178238fs[nullfs] nullfs don't release i-nodes on unlink.
o2012/01/17kern/164261fs[nullfs] [patch] fix panic with NFS served from NULLFS
o2011/11/15kern/162591fs[nullfs] cross-filesystem nullfs does not work as expected
o2011/10/09kern/161424fs[nullfs] __getcwd() calls fail when used on nullfs mount
o2011/06/23kern/158231fs[nullfs] panic on unmounting nullfs mounted over ufs on usb stick that got detached
o2011/03/29kern/156039fs[nullfs] [unionfs] nullfs + unionfs do not compose, result in unlocking unlocked lock
o2009/12/02kern/141091fs[patch] [nullfs] fix panics with DIAGNOSTIC enabled
o2009/02/06kern/131441fs[unionfs] [nullfs] unionfs and/or nullfs not combineable
o2009/01/05kern/130210fs[nullfs] Error by check nullfs
o2008/03/20bin/121898fs[nullfs] pwd(1)/getcwd(2) fails with Permission denied
o2006/10/15sparc64/104428sparc64[nullfs] nullfs panics on E4500 (but not E420)
12 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.