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: syzbot <syzbot+3d2c27c2b7dc2a94814d@syzkaller.appspotmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-kernel@vger.kernel.org, snovitoll@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: [git pull] work.namei stuff (v2)
Date: Sat, 20 Feb 2021 17:40:52 +0000	[thread overview]
Message-ID: <YDFJpF216gaPavrc@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <YDFJKR5uG1N+g9TL@zeniv-ca.linux.org.uk>

Most of that pile is LOOKUP_CACHED series; the rest is a couple of
misc cleanups in the general area...

There's a minor bisect hazard in the end of series, and normally
I would've just folded the fix into the previous commit, but this branch is
shared with Jens' tree, with stuff on top of it in there, so that would've
required rebases outside of vfs.git.

NOTE: I'm less than thrilled by the "let's allow offloading pathwalks
to helper threads" push, but LOOKUP_CACHED is useful on its own.

The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:

  Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.namei

for you to fetch changes up to eacd9aa8cedeb412842c7b339adbaa0477fdd5ad:

  fix handling of nd->depth on LOOKUP_CACHED failures in try_to_unlazy* (2021-02-20 12:33:12 -0500)

----------------------------------------------------------------
Al Viro (3):
      do_tmpfile(): don't mess with finish_open()
      saner calling conventions for unlazy_child()
      fix handling of nd->depth on LOOKUP_CACHED failures in try_to_unlazy*

Jens Axboe (3):
      fs: make unlazy_walk() error handling consistent
      fs: add support for LOOKUP_CACHED
      fs: expose LOOKUP_CACHED through openat2() RESOLVE_CACHED

Steven Rostedt (VMware) (1):
      fs/namei.c: Remove unlikely of status being -ECHILD in lookup_fast()

 fs/namei.c                   | 89 ++++++++++++++++++++++----------------------
 fs/open.c                    |  6 +++
 include/linux/fcntl.h        |  2 +-
 include/linux/namei.h        |  1 +
 include/uapi/linux/openat2.h |  4 ++
 5 files changed, 56 insertions(+), 46 deletions(-)

  reply	other threads:[~2021-02-20 17:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 16:18 WARNING in iov_iter_revert (2) syzbot
2021-02-20 14:25 ` syzbot
     [not found]   ` <CAHk-=wiEBTD884i-U9DU7aDdRxXuz66Q1r-rKTiJUzZoYFgp+g@mail.gmail.com>
2021-02-20 17:38     ` Al Viro
2021-02-20 17:40       ` Al Viro [this message]
2021-02-21 17:43         ` [git pull] work.namei stuff (v2) Linus Torvalds
2021-02-21 18:39         ` pr-tracker-bot
2021-02-20 19:29       ` WARNING in iov_iter_revert (2) Al Viro
2021-02-20 19:40         ` Al Viro
2021-02-21  0:45         ` Linus Torvalds
2021-02-21  8:37           ` Sabyrzhan Tasbolatov
2021-02-21 17:20           ` Linus Torvalds

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=YDFJpF216gaPavrc@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snovitoll@gmail.com \
    --cc=syzbot+3d2c27c2b7dc2a94814d@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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.