linux-kernel - Re: [PATCH -V18 04/13] vfs: Allow handle based open on symlinks

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]

Message-ID: <20100824131919.GA25706@fieldses.org>
Date:	Tue, 24 Aug 2010 09:19:19 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Nick Piggin <npiggin@...nel.dk>
Cc:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>,
	Neil Brown <neilb@...e.de>, Al Viro <viro@...IV.linux.org.uk>,
	Christoph Hellwig <hch@...radead.org>, adilger@....com,
	corbet@....net, hooanon05@...oo.co.jp, miklos@...redi.hu,
	linux-fsdevel@...r.kernel.org, sfrench@...ibm.com,
	philippe.deniel@....FR, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -V18 04/13] vfs: Allow handle based open on symlinks

On Tue, Aug 24, 2010 at 05:21:55PM +1000, Nick Piggin wrote:
> Right. Is this a really important goal, I'm wondering? Is it realistic
> (ie. to be able to remove the nfs server from the kernel)?

I think so.

The hardest part is if you want to export a filesystem that also has
non-nfs users--in the kernel it's much easier to maintain consistency
between local users of the filesystem and nfs clients.

If the server has no local users, then userspace may turn out to be
easier.

In that case you might ask why the server needs a real filesystem to
export at all--in theory it could maintain all its data on its own.  But
I suspect if you try that you find you're reinventing a lot of wheels.

--b.
--
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/