All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [git pull] vfs patches from Miklos
Date: Tue, 2 Jun 2020 01:09:45 +0100	[thread overview]
Message-ID: <20200602000945.GI23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAHk-=wjQ8vRE3jSby=KOejXORsL2qgQ2g=KQ=Y10NvVoVBFtxQ@mail.gmail.com>

On Mon, Jun 01, 2020 at 04:46:45PM -0700, Linus Torvalds wrote:
> On Mon, Jun 1, 2020 at 11:40 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> >         Assorted patches from Miklos; an interesting part here is /proc/mounts
> > stuff...
> 
> You know, this could really have done with more of a real description, Al...

Umm...  Assorted VFS work:
	* faster /proc/*/mount* iterator - insert a cursor into the list
instead of rescan in event of any change
	* several mount options parser cleanups
	* statx patches, including the ability to report mnt_id on statx(2)
	* introduction of faccessat2(2)
	* utimensat(2) with AT_EMPTY_PATH
	* allow creating whiteouts (via mknod(2)) for non-root
	* an aio bugfix
That stuff is really all over the place - there are several groups of related
patches, but the above is about as far as it can be compacted...

  reply	other threads:[~2020-06-02  0:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 18:40 [git pull] vfs patches from Miklos Al Viro
2020-06-01 23:46 ` Linus Torvalds
2020-06-02  0:09   ` Al Viro [this message]
2020-06-01 23:55 ` pr-tracker-bot

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=20200602000945.GI23230@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.