Bug 10856
Summary: | incorrect tracking of overwritten files of running processes in /proc/<pid>/ | ||
---|---|---|---|
Product: | File System | Reporter: | Mike Frysinger (vapier) |
Component: | VFS | Assignee: | fs_vfs |
Status: | RESOLVED WILL_NOT_FIX | ||
Severity: | normal | CC: | adobriyan, akpm, alan, ebiederm |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Mike Frysinger
2008-06-04 13:57:03 UTC
That's weird. Might be hard to fix, I suspect. Maybe Alexey has time to have a think about it? bugme-daemon@bugzilla.kernel.org writes: > http://bugzilla.kernel.org/show_bug.cgi?id=10856 > > > akpm@osdl.org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |akpm@osdl.org, > | |ebiederm@xmission.com, > | |adobriyan@gmail.com > > > > > ------- Comment #1 from akpm@osdl.org 2008-06-04 14:04 ------- > That's weird. Might be hard to fix, I suspect. > > Maybe Alexey has time to have a think about it? The issue has everything to do with how d_move is implemented. /proc/ itself is fine. At first glance it appears this will require some serious surgery in d_move, to fix. Eric don't know why this was closed ... issue (as documented in summary) is still reproducible with a 3.4-rc6 kernel Because reading through the threads beyond it there was no consensus it was even a bug, no agreement what should happen and no plan to fix it. And its now four years later, so its both ABI and obsolete. Make sense ? It's very very hard to fix, and not worth the effort or impact on real code paths that actually get used if you think otherwise - send patches to the vfs list! |