From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, linkinjeon@kernel.org,
Yuezhang.Mo@sony.com, Rochan Avlur <rochan.avlur@gmail.com>
Subject: Re: [PATCH 6.18.y] exfat: preserve benign secondary entries during rename and move
Date: Sun, 19 Jul 2026 11:00:24 -0400 [thread overview]
Message-ID: <20260718192718.0010-stable-reply@kernel.org> (raw)
In-Reply-To: <20260716165127.2998-1-rochan.avlur@gmail.com>
> Commit 8258ef28001a ("exfat: handle unreconized benign secondary
> entries") added cluster freeing for benign secondary entries inside
> exfat_remove_entries(). However, exfat_remove_entries() is also called
> from the rename and move paths (exfat_rename_file and exfat_move_file),
> where the old entry set is being relocated rather than deleted.
Queued for 6.18, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-19 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 14:41 FAILED: patch "[PATCH] exfat: preserve benign secondary entries during rename and" failed to apply to 6.18-stable tree gregkh
2026-07-16 16:51 ` [PATCH 6.18.y] exfat: preserve benign secondary entries during rename and move Rochan Avlur
2026-07-19 15:00 ` Sasha Levin [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=20260718192718.0010-stable-reply@kernel.org \
--to=sashal@kernel.org \
--cc=Yuezhang.Mo@sony.com \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@kernel.org \
--cc=rochan.avlur@gmail.com \
--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