From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>,
Daehyeon Ko <4ncienth@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] fs: make sure to call fsnotify_inoderemove() only once when inode is dead
Date: Fri, 04 Sep 2026 13:00:46 +0200 [thread overview]
Message-ID: <20260904-hermachen-altgedienten-aalen-e790d524ea6a@brauner> (raw)
In-Reply-To: <20260902164924.1333135-2-jack@suse.cz>
On Wed, 02 Sep 2026 18:49:25 +0200, Jan Kara wrote:
> fs: make sure to call fsnotify_inoderemove() only once when inode is dead
Sheesh. Not pretty. :)
---
Applied to the vfs-7.4.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.4.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-7.4.misc
[1/1] fs: make sure to call fsnotify_inoderemove() only once when inode is dead
https://git.kernel.org/vfs/vfs/c/669bb5af15d4
prev parent reply other threads:[~2026-09-04 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:49 [PATCH] fs: make sure to call fsnotify_inoderemove() only once when inode is dead Jan Kara
2026-09-04 11:00 ` 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=20260904-hermachen-altgedienten-aalen-e790d524ea6a@brauner \
--to=brauner@kernel.org \
--cc=4ncienth@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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