linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] mount_setattr updates
Date: Tue, 29 Jun 2021 14:35:11 +0200	[thread overview]
Message-ID: <20210629123511.1191153-1-christian.brauner@ubuntu.com> (raw)

Hi Linus,

/* Summary */
A few releases ago the old mount API gained support for a mount options which
prevents following symlinks on a given mount. This adds support for it in the
new mount api through the MOUNT_ATTR_NOSYMFOLLOW flag via mount_setattr() and
fsmount(). With mount_setattr() that flag can even be applied recursively.

There's an additional ack from Ross Zwisler who originally authored the
nosymfollow patch. As I've already had the patches in my for-next I didn't add
his ack explicitly.

/* Testing */
All patches are based on v5.13-rc4 and have been sitting in linux-next. No
build failures or warnings were observed. All old and new tests are passing.

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

The following changes since commit 8124c8a6b35386f73523d27eacb71b5364a68c4c:

  Linux 5.13-rc4 (2021-05-30 11:58:25 -1000)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/fs.mount_setattr.nosymfollow.v5.14

for you to fetch changes up to 5990b5d770cbfe2b4254d870240e9863aca421e3:

  tests: test MOUNT_ATTR_NOSYMFOLLOW with mount_setattr() (2021-06-01 15:06:51 +0200)

Please consider pulling these changes from the signed fs.mount_setattr.nosymfollow.v5.14 tag.

Thanks!
Christian

----------------------------------------------------------------
fs.mount_setattr.nosymfollow.v5.14

----------------------------------------------------------------
Christian Brauner (2):
      mount: Support "nosymfollow" in new mount api
      tests: test MOUNT_ATTR_NOSYMFOLLOW with mount_setattr()

 fs/namespace.c                                     |  9 ++-
 include/uapi/linux/mount.h                         |  1 +
 .../selftests/mount_setattr/mount_setattr_test.c   | 88 +++++++++++++++++++++-
 3 files changed, 92 insertions(+), 6 deletions(-)

             reply	other threads:[~2021-06-29 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 12:35 Christian Brauner [this message]
2021-06-30  3:35 ` [GIT PULL] 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:
  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=20210629123511.1191153-1-christian.brauner@ubuntu.com \
    --to=christian.brauner@ubuntu.com \
    --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;
as well as URLs for NNTP newsgroup(s).