linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Jan Kara <jack@suse.cz>,
	Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] Rename and export some vfs helpers
Date: Fri,  8 Sep 2023 16:28:58 +0300	[thread overview]
Message-ID: <20230908132900.2983519-1-amir73il@gmail.com> (raw)

Christian,

This is the rename that you proposed, for the helpers needed by
overlayfs.

I could stage this in the overlayfs tree for 6.7, but it has a bit
of conflict potential, so maybe best if you stage this in vfs tree.

Perhaps on a topic branch that is expected to be a little more steady
than 'vfs.misc', so that I can base overlayfs-next on it?

Thanks,
Amir.


Amir Goldstein (2):
  fs: rename __mnt_{want,drop}_write*() helpers
  fs: export mnt_{get,put}_write_access() to modules

 fs/inode.c            |  8 ++++----
 fs/internal.h         | 12 ++++++------
 fs/namespace.c        | 36 +++++++++++++++++++-----------------
 fs/open.c             |  2 +-
 include/linux/mount.h |  4 ++--
 kernel/acct.c         |  4 ++--
 6 files changed, 34 insertions(+), 32 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-09-08 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 13:28 Amir Goldstein [this message]
2023-09-08 13:28 ` [PATCH 1/2] fs: rename __mnt_{want,drop}_write*() helpers Amir Goldstein
2023-09-08 13:29 ` [PATCH 2/2] fs: export mnt_{get,put}_write_access() to modules Amir Goldstein
2023-09-11 13:09 ` [PATCH 0/2] Rename and export some vfs helpers Christian Brauner

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=20230908132900.2983519-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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 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).