PRs for tag 'ffs'
This is an experimental report containing PRs for tag 'ffs' as of 5-30-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 'ffs':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/03/11 | kern/165950 | fs | [ffs] SU+J and fsck problem |
| o | 2009/07/20 | kern/136944 | fs | [ffs] [lor] bufwait/snaplk (fsync) |
| o | 2008/07/23 | kern/125895 | fs | [ffs] [panic] kernel: panic: ffs_blkfree: freeing free block |
| o | 2008/05/18 | kern/123778 | vwe | [panic] [ffs] [msgs] server reboots when running 130.clean-msgs |
| o | 2008/04/02 | kern/122380 | fs | [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash mem) |
| o | 2007/09/23 | kern/116583 | fs | [ffs] [hang] System freezes for short time when using mmap on full filesystem |
| o | 2006/01/24 | kern/92272 | fs | [ffs] [hang] Filling a filesystem while creating a snapshot on it locks the system |
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.