From: Hyunchul Lee <hyc.lee@gmail.com>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
ntfs@lists.linux.dev, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ntfs: fix two kmap_local bugs on 32-bit kernels
Date: Tue, 6 Oct 2026 15:04:08 +0900 [thread overview]
Message-ID: <asSPWFQM60is9C0-@hyunchul-PC02> (raw)
In-Reply-To: <20261006045136.5911-1-kmehltretter@gmail.com>
On Tue, Oct 06, 2026 at 06:51:34AM +0200, Karl Mehltretter wrote:
> Two kmap_local bugs in the mount path of fs/ntfs. Both only show on
> 32-bit kernels with HIGHMEM, where kmap_local_folio() hands out fixmap
> slots from a per task stack of 16 entries. multi_v7_defconfig enables
> both NTFS_FS and HIGHMEM, so the stock 32-bit ARM configuration is
> affected.
>
> Patch 1: check_mft_mirror() unmaps pointers that were advanced past the
> end of the page. On 32-bit ARM this clears the wrong fixmap entry and
> the mount dies with a BUG a few calls later. syzkaller found it on a
> multi_v7_defconfig kernel. A fresh mkntfs volume reproduces it on the
> first mount.
>
> Patch 2: ntfs_check_logfile() maps the same page once per loop
> iteration and unmaps it once, so a mount leaves three entries on the
> stack of the mounting task. After one mount the CPU it ran on can no
> longer be taken offline. A process that mounts ntfs volumes five times
> hits the BUG_ON() in kmap_local_idx_push(). x86-32 also warns when
> mount(2) returns.
>
> The two fixes are independent of each other. Patch 2 was tested on top
> of patch 1. Both were tested on 32-bit ARM and x86-32 in QEMU. Details
> are below the --- line of each patch.
>
> Changes in v2:
> - v1 carried an older copy of patch 2 as a second 2/2 by mistake. The
> patches are unchanged.
>
> v1:
> https://lore.kernel.org/r/20261006043810.5393-1-kmehltretter@gmail.com/
>
> Karl Mehltretter (2):
> ntfs: fix kunmap_local() of advanced pointers in check_mft_mirror()
> ntfs: fix kmap_local leak in ntfs_check_logfile()
The whole series look good to me.
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
>
> fs/ntfs/logfile.c | 11 ++++++-----
> fs/ntfs/super.c | 20 +++++++++++---------
> 2 files changed, 17 insertions(+), 14 deletions(-)
>
>
> base-commit: 551c722f40809618230001baccf219193e22fc5a
> --
> 2.53.0
>
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-10-06 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 4:51 Karl Mehltretter
2026-10-06 4:51 ` [PATCH v2 1/2] ntfs: fix kunmap_local() of advanced pointers in check_mft_mirror() Karl Mehltretter
2026-10-06 4:51 ` [PATCH v2 2/2] ntfs: fix kmap_local leak in ntfs_check_logfile() Karl Mehltretter
2026-10-06 6:04 ` Hyunchul Lee [this message]
2026-10-06 13:29 ` [PATCH v2 0/2] ntfs: fix two kmap_local bugs on 32-bit kernels 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=asSPWFQM60is9C0-@hyunchul-PC02 \
--to=hyc.lee@gmail.com \
--cc=kmehltretter@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--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
all inboxes | Powered by JetHome®