mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git d_path series
Date: Sat, 3 Jul 2021 02:56:05 +0000	[thread overview]
Message-ID: <YN/RxStDmizrFH/m@zeniv-ca.linux.org.uk> (raw)

	d_path.c refactoring

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the git repository at:

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

for you to fetch changes up to e4b275531887fef7f7d8a7284bfc32f0fbbd4208:

  getcwd(2): clean up error handling (2021-05-18 20:15:58 -0400)

----------------------------------------------------------------
Al Viro (14):
      d_path: "\0" is {0,0}, not {0}
      d_path: saner calling conventions for __dentry_path()
      d_path: regularize handling of root dentry in __dentry_path()
      d_path: get rid of path_with_deleted()
      getcwd(2): saner logics around prepend_path() call
      d_path: don't bother with return value of prepend()
      d_path: lift -ENAMETOOLONG handling into callers of prepend_path()
      d_path: make prepend_name() boolean
      d_path: introduce struct prepend_buffer
      d_path: prepend_path(): get rid of vfsmnt
      d_path: prepend_path(): lift resetting b in case when we'd return 3 out of loop
      d_path: prepend_path(): lift the inner loop into a new helper
      d_path: prepend_path() is unlikely to return non-zero
      getcwd(2): clean up error handling

 fs/d_path.c | 324 +++++++++++++++++++++++++-----------------------------------
 1 file changed, 133 insertions(+), 191 deletions(-)

             reply	other threads:[~2021-07-03  2:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  2:56 Al Viro [this message]
2021-07-03 19:40 ` 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=YN/RxStDmizrFH/m@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®