public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] fs mount_setattr for v5.17-rc4
Date: Sat, 19 Feb 2022 12:53:29 +0100	[thread overview]
Message-ID: <20220219115327.3635609-1-brauner@kernel.org> (raw)

Hi Linus,

/* Summary */
This contains a fix for one of the selftests for the mount_setattr syscall to
create idmapped mounts, an entry for idmapped mounts for maintainers, and
missing kernel documentation for the helper we split out some time ago to get
and yield write access to a mount when changing mount properties.
There's additional cleanup to simplify the codeflow when (recursively) changing
mount properties which can simply be delayed until the next merge window. I've
been traveling so sending PRs is a bit delayed.

/* Testing */
All patches are based on v5.17-rc2 and have been sitting in linux-next. No
build failures or warnings were observed.

/* Conflicts */
At the time of creating this PR no merge conflicts showed up doing a test-merge
with current mainline.

The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:

  Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/fs.mount_setattr.v5.17-rc4

for you to fetch changes up to 538f4f022a4612f969d5324ee227403c9f8b1d72:

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

Please consider pulling these changes from the signed fs.mount_setattr.v5.17-rc4 tag.

Thanks!
Christian

----------------------------------------------------------------
fs.mount_setattr.v5.17-rc4

----------------------------------------------------------------
Christian Brauner (3):
      tests: fix idmapped mount_setattr test
      MAINTAINERS: add entry for idmapped mounts
      fs: add kernel doc for mnt_{hold,unhold}_writers()

 MAINTAINERS                                        |  9 +++++++
 fs/namespace.c                                     | 30 ++++++++++++++++++++++
 .../selftests/mount_setattr/mount_setattr_test.c   |  4 +--
 3 files changed, 41 insertions(+), 2 deletions(-)

             reply	other threads:[~2022-02-19 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 11:53 Christian Brauner [this message]
2022-02-20 19:06 ` [GIT PULL] fs mount_setattr for v5.17-rc4 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=20220219115327.3635609-1-brauner@kernel.org \
    --to=brauner@kernel.org \
    --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