Linux-Fsdevel Archive on
 help / color / Atom feed
From: Amir Goldstein <>
To: Al Viro <>
	linux-fsdevel <>,
	Miklos Szeredi <>,
	David Howells <>,
	"Eric W. Biederman" <>,
	Aleksa Sarai <>,
	Jeff Layton <>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] sorting pathwalk semantics out
Date: Fri, 14 Feb 2020 20:27:37 +0200
Message-ID: <> (raw)
In-Reply-To: <>


Just making this public as requested, so potential attendees can chime in.
I suppose this was your intention.


On Fri, Feb 14, 2020 at 7:09 AM Al Viro <> 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
> _______________________________________________
> Lsf-pc mailing list

           reply index

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Fsdevel Archive on

Archives are clonable:
	git clone --mirror linux-fsdevel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fsdevel linux-fsdevel/ \
	public-inbox-index linux-fsdevel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone