On Mon, Jun 07, 2010 at 11:53:28AM -0700, Linus Torvalds wrote: > > > On Mon, 7 Jun 2010, Al Viro wrote: > > > > Ho-hum... Speaking of which, what about leak fixes? There's a long-standing > > in-core inode leak in jffs2; basically, if you fail directory modification > > in symlink() et.al., you get a leaked inode and whinge at umount. Found > > after -rc1, had been there since all the way back (similar bug in creat() > > had been fixed in 2003, mkdir()/mknod()/symlink() were not). Fix sits in > > jffs2-fixes now... > > I think a leak that is trivial easily falls under "security issue" as a > potential DoS issue. > > On the other hand, if it's not trivially fixed (say it needs big > re-organizing of some locking or refcounting or whatever), and it's a > really slow leak of a pretty small data structure, and is not triggered by > normal users (say, you need to mount a filesystem or it needs some very > specific timing), I think it falls under "we haven't seen in the previous > five years, we might as well make sure the fix is tested in the next merge > window". You need something like IO errors or device being full to trigger it. As for the fix, it's basically a matter of "set i_nlink to 0 and iput() instead of manual jffs2_clear_inode(); sure, you want to kill the on-disk inode, but you want in-core one gone too". Basically, that's what all local filesystems are doing to clean up after such error and that's what jffs2 is doing for ->create(). As for the other stuff in that tree... There's a fix for nfsd/create race (rather narrow and not trivial to hit, but capable of fs corruption) and there's mtd stuff I've no fscking clue about. If not for the mtd part I'd simply pulled it in my tree. As it is... I still can do that (done that for current semi-private branch), but I'd prefer to avoid feeding mtd stuff through vfs tree, for all the obvious reasons. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
