From: Amir Goldstein <amir73il@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Aleksa Sarai <cyphar@cyphar.com>,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] sorting pathwalk semantics out
Date: Fri, 14 Feb 2020 20:27:37 +0200 [thread overview]
Message-ID: <CAOQ4uxiEQd00U75=AkXHaEd+OKMFMor4JdDaN2j6fauKVy_L3w@mail.gmail.com> (raw)
In-Reply-To: <20200214050853.GX23230@ZenIV.linux.org.uk>
Al,
Just making this public as requested, so potential attendees can chime in.
I suppose this was your intention.
Thanks,
Amir.
On Fri, Feb 14, 2020 at 7:09 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> There had been quite a bit of activity around that area
> (openat2() series, for example) and IMO the complexity in the damn
> thing is getting close to critical - we are not quite at the point
> where the average amount of bugs introduced by fixing a bug is greater
> than one, but it's uncomfortably close. Quite a few places are
> far too subtle and convoluted (anything related to do_last(), for
> one thing).
>
> We need to get that mess under control. I have a (still
> growing) series massaging it to somewhat saner shape, but there
> are some interesting dark corners that need to be sorted out (situation
> around mount traps, for example).
>
> We definitely need to settle on some description of semantics.
> Preferably with a set of litmus tests, similar to what memory model
> folks had been doing.
>
> I would like to catch at least the people who'd been active
> around that area. Miklos Szeredi (due to atomic_open involvement,
> if nothing else), David Howells and Ian Kent (mount traps, among
> other things), Eric Biederman (userns fallouts of all sorts),
> Aleksa Sarai (openat2 - most recent large changes in the whole
> thing), Jeff Layton (revalidation et.al.)...
> _______________________________________________
> Lsf-pc mailing list
> Lsf-pc@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
parent reply other threads:[~2020-02-14 18:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200214050853.GX23230@ZenIV.linux.org.uk>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOQ4uxiEQd00U75=AkXHaEd+OKMFMor4JdDaN2j6fauKVy_L3w@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).