From: 이상호 <kudo3228@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Sangho Lee <kudo3228@gmail.com>, Hyunchul Lee <hyc.lee@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG/RFC] ntfs: crafted image triggers WARN_ON in ntfs_map_runlist_nolock()
Date: Fri, 3 Jul 2026 12:39:14 +0900 [thread overview]
Message-ID: <20260703033914.98698-1-kudo3228@gmail.com> (raw)
In-Reply-To: <CAKYAXd_zqD8dGrApqpR-ZRvqU1JnVYaXLM9JH2PjJXaekgJgEQ@mail.gmail.com>
From: Sangho Lee <kudo3228@gmail.com>
Hi Namjae,
Thanks for the patch.
I applied it to my NTFS test tree and rebuilt the kernel. I then reran
syz-repro with the same syzkaller crash log that reproduced the original
WARN_ON in ntfs_map_runlist_nolock() on the unpatched kernel.
Result:
- unpatched kernel: the same log reproduced the WARN_ON in
ntfs_map_runlist_nolock()
- patched kernel: syz-repro ran through all extraction phases for 29m28s
and failed to reproduce the warning:
- 15s single runs: no crash
- 15s grouped/bisect: did not crash
- 1m40s single runs: no crash
- 1m55s grouped/bisect: did not crash
- 6m single runs: no crash
- 6m15s grouped/bisect: did not crash
- no kernel WARNING/Oops/BUG lines were observed
The change also matches the root cause I saw: when ctx_needs_reset is true,
ntfs_map_runlist_nolock() can reach the runlist mapping path for a resident
attribute. Returning -EIO before using the non-resident mapping fields avoids
triggering the WARN_ON and prevents the invalid path.
So yes, this patch fixes the issue from my side.
Tested-by: Sangho Lee <kudo3228@gmail.com>
Thanks,
Sangho
next prev parent reply other threads:[~2026-07-03 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 22:12 [BUG/RFC] ntfs: crafted image triggers WARN_ON in ntfs_map_runlist_nolock() 이상호
2026-07-01 23:36 ` Namjae Jeon
2026-07-02 1:37 ` Namjae Jeon
2026-07-03 3:39 ` 이상호 [this message]
2026-07-03 4:41 ` Namjae Jeon
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=20260703033914.98698-1-kudo3228@gmail.com \
--to=kudo3228@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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