All of
 help / color / mirror / Atom feed
From: Christian Brauner <>
To: Linus Torvalds <>
Subject: [GIT PULL] fs/mount_setattr updates
Date: Wed, 23 Mar 2022 12:02:09 +0100	[thread overview]
Message-ID: <> (raw)

Hey Linus,

/* Summary */
This contains a few more patches to massage the mount_setattr() codepaths and
one minor fix to reuse a helper we added some time back. The final two patches
do similar cleanups in different ways. One patch is mine and the other is Al's
who was nice enough to give me a branch for it. Since his came in later and my
branch had been sitting in -next for quite some time we just put his on top
instead of swap them.

/* Testing */
All patches are based on v5.17-rc2 and have been sitting in linux-next. No
build failures or warnings were observed and fstests and selftests have seen no
regressions caused by this patchset.

/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with current

The following changes since commit 538f4f022a4612f969d5324ee227403c9f8b1d72:

  fs: add kernel doc for mnt_{hold,unhold}_writers() (2022-02-14 08:35:32 +0100)

are available in the Git repository at: tags/fs.v5.18

for you to fetch changes up to e257039f0fc7da36ac3a522ef9a5cb4ae7852e67:

  mount_setattr(): clean the control flow and calling conventions (2022-03-15 19:17:13 -0400)

Please consider pulling these changes from the signed fs.v5.18 tag.



Al Viro (1):
      mount_setattr(): clean the control flow and calling conventions

Christian Brauner (4):
      fs: add mnt_allow_writers() and simplify mount_setattr_prepare()
      fs: simplify check in mount_setattr_commit()
      fs: don't open-code mnt_hold_writers()
      fs: clean up mount_setattr control flow

 fs/namespace.c | 148 ++++++++++++++++++++++++++++++---------------------------
 1 file changed, 78 insertions(+), 70 deletions(-)

             reply	other threads:[~2022-03-23 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 11:02 Christian Brauner [this message]
2022-03-24 19:44 ` [GIT PULL] fs/mount_setattr updates 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:

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

  git send-email \ \ \ \ \ \

* 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.