All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: Seth Forshee <seth.forshee@digitalocean.com>,
	Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>
Subject: [PATCH 0/7] mount_setattr fixes
Date: Thu,  3 Feb 2022 14:14:04 +0100	[thread overview]
Message-ID: <20220203131411.3093040-1-brauner@kernel.org> (raw)

Hey,

This contains a couple of minor fixes for the mount_setattr() code I
didn't get around to sending so far. Apart from making the control flow
a little easier to follow there's a fix for a long-standing braino in
one of the idmapped mount kernel selftests. The kernel selftests are
separate from the large fstests suite and are only concerned with
testing the syscall itself whereas the fstests test all related vfs and
filesystem specific functionality for idmapped mounts. I would also like
to add a maintenance entry for idmapped mounts for the few files and
documentation that I've written.
I'll be gone for ~10 days starting next week but I'll try to check-in
regularly.

Thanks!
Christian

Christian Brauner (7):
  tests: fix idmapped mount_setattr test
  MAINTAINERS: add entry for idmapped mounts
  fs: add kernel doc for mnt_{hold,unhold}_writers()
  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

 MAINTAINERS                                   |   9 ++
 fs/namespace.c                                | 148 +++++++++++-------
 .../mount_setattr/mount_setattr_test.c        |   4 +-
 3 files changed, 105 insertions(+), 56 deletions(-)


base-commit: 26291c54e111ff6ba87a164d85d4a4e134b7315c
-- 
2.32.0


             reply	other threads:[~2022-02-03 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 13:14 Christian Brauner [this message]
2022-02-03 13:14 ` [PATCH 1/7] tests: fix idmapped mount_setattr test Christian Brauner
2022-02-07  6:50   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 2/7] MAINTAINERS: add entry for idmapped mounts Christian Brauner
2022-02-07  6:50   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 3/7] fs: add kernel doc for mnt_{hold,unhold}_writers() Christian Brauner
2022-02-07  6:51   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 4/7] fs: add mnt_allow_writers() and simplify mount_setattr_prepare() Christian Brauner
2022-02-07  6:51   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 5/7] fs: simplify check in mount_setattr_commit() Christian Brauner
2022-02-07  6:52   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 6/7] fs: don't open-code mnt_hold_writers() Christian Brauner
2022-02-07  6:52   ` Christoph Hellwig
2022-02-03 13:14 ` [PATCH 7/7] fs: clean up mount_setattr control flow Christian Brauner
2022-02-07  6:53   ` Christoph Hellwig

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=20220203131411.3093040-1-brauner@kernel.org \
    --to=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=seth.forshee@digitalocean.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.