On Fri, Jan 14, 2011 at 2:24 PM, Nick Piggin <npiggin@xxxxxxxxx> wrote: > Git tree is here: > > git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git > > Branch is: > > vfs-scale-working > > Head: > 657e94b673a805b427903c5628e95348235fad06 > > Diffstat: > Documentation/filesystems/porting | 8 ++++---- > Documentation/filesystems/vfs.txt | 4 ++-- > fs/namei.c | 18 ++++++++++++++++++ > fs/nfs/dir.c | 6 +++++- > include/linux/list_bl.h | 5 +++-- > include/linux/rculist_bl.h | 3 ++- > 6 files changed, 34 insertions(+), 10 deletions(-) > > Just bug fixes, importantly nfs chroot one that several people are hitting. > > d_set_d_op bugs *should* be a thing of the past after the dust settles > from Al's work, so I'm leaving that area alone. > > Remaining known bug is an nfsd oops when exporting filesystems that > supply a .d_revalidate(), which is not going to be a common configuration > and I'd like to do a d_revalidate API change to fix it, so don't want to > rush that through. IOW, I think it would be OK to do an -rc1 with this known issue. There were no reports of that bug triggering, it was just by review from J. R. Okajima. .d_revalidate filesystems tend to be network and cluster and such, so it won't even affect a large proportion of nfsd servers. It definitely *will* oops if somebody exports a .d_revalidate filesystem, but it will be a clean NULL deref, at least. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
