From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
Mimi Zohar <zohar@linux.ibm.com>,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Reduce impact of overlayfs backing files fake path
Date: Tue, 10 Oct 2023 13:52:09 +0200 [thread overview]
Message-ID: <20231010-lohnen-botanik-7bf974a5cecd@brauner> (raw)
In-Reply-To: <20231009153712.1566422-1-amir73il@gmail.com>
On Mon, 09 Oct 2023 18:37:09 +0300, Amir Goldstein wrote:
> Following v3 addresses Al's review comments on v2.
>
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/3] fs: get mnt_writers count for an open backing file's real path
https://git.kernel.org/vfs/vfs/c/90e168d5fa01
[2/3] fs: create helper file_user_path() for user displayed mapped file path
https://git.kernel.org/vfs/vfs/c/842b845c7657
[3/3] fs: store real path instead of fake path in backing file f_path
https://git.kernel.org/vfs/vfs/c/6b9503cf48c9
prev parent reply other threads:[~2023-10-10 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 15:37 [PATCH v3 0/3] Reduce impact of overlayfs backing files fake path Amir Goldstein
2023-10-09 15:37 ` [PATCH v3 1/3] fs: get mnt_writers count for an open backing file's real path Amir Goldstein
2023-10-09 15:37 ` [PATCH v3 2/3] fs: create helper file_user_path() for user displayed mapped file path Amir Goldstein
2023-10-09 15:37 ` [PATCH v3 3/3] fs: store real path instead of fake path in backing file f_path Amir Goldstein
2023-10-10 11:59 ` Miklos Szeredi
2023-10-10 13:10 ` Amir Goldstein
2023-10-10 13:17 ` Amir Goldstein
2023-10-10 13:34 ` Miklos Szeredi
2023-10-10 15:22 ` Amir Goldstein
2023-10-10 16:55 ` Al Viro
2023-10-10 17:41 ` Al Viro
2023-10-10 17:57 ` Amir Goldstein
2023-10-10 18:21 ` Al Viro
2023-10-10 18:28 ` Amir Goldstein
2023-10-11 1:26 ` Al Viro
2023-10-10 18:14 ` Miklos Szeredi
2023-10-11 1:37 ` Al Viro
2023-10-10 11:52 ` Christian Brauner [this message]
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=20231010-lohnen-botanik-7bf974a5cecd@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.ibm.com \
/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).