From: Christian Brauner <brauner@kernel.org>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Guidong Han <2045gemini@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Jann Horn <jannh@google.com>,
Qi Tang <tpluszz77@gmail.com>,
Junxi Qian <qjx1298677004@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eventpoll: pin files while checking reverse paths
Date: Thu, 23 Jul 2026 12:53:20 +0200 [thread overview]
Message-ID: <20260723-blaulicht-datum-bissfest-0d4b5058d225@brauner> (raw)
In-Reply-To: <20260718104406.27897-1-2045gemini@gmail.com>
On Sat, 18 Jul 2026 18:44:06 +0800, Guidong Han wrote:
> eventpoll: pin files while checking reverse paths
Thanks, this is a good bug report.
---
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes 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.fixes
[1/1] eventpoll: pin files while checking reverse paths
https://git.kernel.org/vfs/vfs/c/5d26e9caedff
next prev parent reply other threads:[~2026-07-23 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 10:44 Guidong Han
2026-07-23 10:53 ` Christian Brauner [this message]
2026-07-23 18:06 ` David Laight
2026-07-24 3:23 ` Guidong Han
2026-07-23 19:50 ` Mateusz Guzik
2026-07-24 3:57 ` Guidong Han
2026-07-24 14:54 ` Mateusz Guzik
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=20260723-blaulicht-datum-bissfest-0d4b5058d225@brauner \
--to=brauner@kernel.org \
--cc=2045gemini@gmail.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qjx1298677004@gmail.com \
--cc=tpluszz77@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®