From: Sasha Levin <sashal@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Daehyeon Ko <4ncienth@gmail.com>,
Jan Kara <jack@suse.cz>,
"Christian Brauner (Amutable)" <brauner@kernel.org>
Subject: Re: [PATCH 6.6.y] fs: make sure to call fsnotify_inoderemove() only once when inode is dead
Date: Tue, 10 Nov 2026 10:24:01 -0500 [thread overview]
Message-ID: <20261110152402.2141028-2-sashal@kernel.org> (raw)
In-Reply-To: <CAOQ4uxi7xkQiYtjQNuso0MC6KGGpwGbd+xST5NQ_aYOtaoAixg@mail.gmail.com>
On Tue, Nov 10, 2026 at 09:10:17AM +0100, Amir Goldstein wrote:
> Please drop this patch from all stable kernels or apply only together
> with the followup fix.
For 7.3, 6.18 and 6.12 the backport tooling picked a522dd871024 together with
669bb5af15d4. Both were added to those queues in the same commit, a522dd871024
sits after 669bb5af15d4 in each series, and both are in the current 7.3.4-rc1,
6.18.63-rc1 and 6.12.117-rc1.
The 6.6.y backport you replied to was a manual one after the patch failed to
apply. a522dd871024 won't apply to it as-is, so I'm holding the 6.6.y backport
until there is a matching backport of a522dd871024.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-10 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 10:28 FAILED: patch "[PATCH] fs: make sure to call fsnotify_inoderemove() only once when inode is dead" failed to apply to 6.6-stable tree Sasha Levin
2026-11-10 3:29 ` [PATCH 6.6.y] fs: make sure to call fsnotify_inoderemove() only once when inode is dead Sasha Levin
2026-11-10 8:10 ` Amir Goldstein
2026-11-10 15:24 ` Sasha Levin [this message]
2026-11-10 15:41 ` Amir Goldstein
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=20261110152402.2141028-2-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=4ncienth@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=stable@vger.kernel.org \
/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