public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: patches@lists.linux.dev, stable@vger.kernel.org,
	syzbot <syzbot+895c23f6917da440ed0d@syzkaller.appspotmail.com>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	ntfs3@lists.linux.dev
Subject: Re: [PATCH AUTOSEL 6.17-5.15] ntfs3: pretend $Extend records as regular files
Date: Tue, 4 Nov 2025 08:56:52 -0500	[thread overview]
Message-ID: <aQoGJP3PsVsq9A4y@laps> (raw)
In-Reply-To: <cde69513-a413-447e-8cb4-5627da29550e@I-love.SAKURA.ne.jp>

On Sun, Oct 26, 2025 at 05:12:23PM +0900, Tetsuo Handa wrote:
>On 2025/10/26 0:55, Sasha Levin wrote:
>> Conclusion: This is a targeted bugfix to comply with VFS invariants and
>> prevent failures when interacting with $Extend records. It’s safe and
>> appropriate to backport to stable kernels that include ntfs3 and the
>> may_open() invariant check.
>
>Please consider waiting for
>https://lkml.kernel.org/r/tencent_F24B651BC22523BA92BB5A337D9E2A1B5F08@qq.com
>to arrive at linux.git before backporting "ntfs3: pretend $Extend records
>as regular files".

Looks like that fix still didn't land, so I'll drop this patch.

-- 
Thanks,
Sasha

      reply	other threads:[~2025-11-04 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251025160905.3857885-1-sashal@kernel.org>
2025-10-25 15:55 ` [PATCH AUTOSEL 6.17-5.15] ntfs3: pretend $Extend records as regular files Sasha Levin
2025-10-26  8:12   ` Tetsuo Handa
2025-11-04 13:56     ` 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=aQoGJP3PsVsq9A4y@laps \
    --to=sashal@kernel.org \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=patches@lists.linux.dev \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+895c23f6917da440ed0d@syzkaller.appspotmail.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