From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: popcorn mix <popcornmix@gmail.com>, <ntfs3@lists.linux.dev>,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: Fix memory corruption when page_size changes
Date: Tue, 2 Jul 2024 14:41:23 +0300 [thread overview]
Message-ID: <b41e693f-940b-42a8-8154-1721c7ff13e1@paragon-software.com> (raw)
In-Reply-To: <a60fc742-0ad4-498d-b90f-793b9578b843@leemhuis.info>
On 01.07.2024 15:53, Linux regression tracking (Thorsten Leemhuis) wrote:
> [CCing a few lists]
>
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Konstantin, what's the status of this regression report or the patch Dom
> Cobley propsed to fix the issue? From here it looks like it fall through
> the cracks, but I might be missing something.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke
>
> On 14.06.24 18:24, popcorn mix wrote:
>> On Fri, Jun 14, 2024 at 4:55 PM Dom Cobley <popcornmix@gmail.com> wrote:
>>> The kernel panic can be observed when connecting an
>>> ntfs formatted drive that has previously been connected
>>> to a Windows machine to a Raspberry Pi 5, which by defauilt
>>> uses a 16K kernel pagesize.
>> Here are links to some bug reports about the issue:
>> https://github.com/raspberrypi/linux/issues/6036
>> https://forum.libreelec.tv/thread/28620-libreelec-12-0-rpi5-and-ntfs-hdd-problem/?postID=192713#post192713
>> https://forums.raspberrypi.com/viewtopic.php?p=2203090#p2203090
>> https://forums.raspberrypi.com/viewtopic.php?t=367545
>>
>> The common points are it occurs on the (default) 16K pagesize kernel,
>> but switching to 4K pagesize kernel
>> avoids the issue.
>>
>> Issue wasn't present in previous RPiOS LTS kernel (6.1), but is
>> present in current LTS kernel (6.6).
>> Revering to 6.1 kernel avoids the issue.
>>
>> I've confirmed that reverting the commit:
>> 865e7a7700d9 ("fs/ntfs3: Reduce stack usage")
>>
>> avoids the issue.
>>
>> This patch avoids the issue for me, and I'd like confirmation it is correct.
Hello everyone,
I recently accepted this patch with the same fix:
https://lore.kernel.org/ntfs3/20240529064053.2741996-2-chenhuacai@loongson.cn/.
Unfortunately, I don't have an RPi with a pagesize=16K at hand, so I
can't practically test it.
Regards, Konstantin
prev parent reply other threads:[~2024-07-02 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240614155437.2063380-1-popcornmix@gmail.com>
[not found] ` <CAEi1pCSQePMo4X_RvMfYmpxYwmuamhd8=1OXgNCU-N2BBdTXPg@mail.gmail.com>
2024-07-01 12:53 ` Linux regression tracking (Thorsten Leemhuis)
2024-07-02 11:41 ` Konstantin Komarov [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=b41e693f-940b-42a8-8154-1721c7ff13e1@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=popcornmix@gmail.com \
--cc=regressions@lists.linux.dev \
/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®