linux-kernel - Re: Please pull vfs-scale-working tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 Jan 2011 14:41:23 +1100
From:	Nick Piggin <npiggin@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Please pull vfs-scale-working tree

On Fri, Jan 14, 2011 at 2:24 PM, Nick Piggin <npiggin@...il.com> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/