From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>, Jens Axboe <axboe@kernel.dk>
Cc: syzbot <syzbot+1ab243d3eebb2aabf4a4@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] KASAN: null-ptr-deref Read in io_sqe_buffer_register
Date: Fri, 5 Sep 2025 08:34:19 +0200 [thread overview]
Message-ID: <1ebd15f2-b709-483b-ac52-2aa0e963454f@redhat.com> (raw)
In-Reply-To: <20250904202535.fff5bea806408171d349a7f1@linux-foundation.org>
On 05.09.25 05:25, Andrew Morton wrote:
> On Thu, 4 Sep 2025 17:20:41 -0600 Jens Axboe <axboe@kernel.dk> wrote:
>
>>> ==================================================================
>>
>> This is from the mm-unstable changes in linux-next, adding David as I
>> ran a quick bisect and it said:
>>
>> da6b34293ff8dbb78f8b9278c9a492925bbf1f87 is the first bad commit
>> commit da6b34293ff8dbb78f8b9278c9a492925bbf1f87
>> Author: David Hildenbrand <david@redhat.com>
>> Date: Mon Sep 1 17:03:40 2025 +0200
>>
>> mm/gup: remove record_subpages()
>>
>> We can just cleanup the code by calculating the #refs earlier, so we can
>> just inline what remains of record_subpages().
>>
>> Calculate the number of references/pages ahead of times, and record them
>> only once all our tests passed.
>>
>> Link: https://lkml.kernel.org/r/20250901150359.867252-20-david@redhat.com
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>
>> I won't personally have time to look into this until after the weekend,
>> but as it's linux-next specific, not a huge deal right now.
>>
>> Note that there's also a similar report, which is the same thing:
>>
>> https://lore.kernel.org/all/68b9d130.a00a0220.eb3d.0008.GAE@google.com/
>>
>> which I marked as dupe of this one.
>
> Thanks. Seems i can remove that patch without causing merge or build
> damage, so I'll do that.
Thanks, I shall go and figure out what I messed up there. I'll then
reply to the v2 of the patch with a fixup.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-09-05 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 15:36 [syzbot] [io-uring?] KASAN: null-ptr-deref Read in io_sqe_buffer_register syzbot
2025-09-04 23:20 ` Jens Axboe
2025-09-05 3:25 ` Andrew Morton
2025-09-05 6:34 ` David Hildenbrand [this message]
2025-09-05 7:42 ` David Hildenbrand
2025-09-05 9:41 ` syzbot
2025-09-05 10:04 ` David Hildenbrand
2025-09-05 10:48 ` syzbot
2025-09-06 2:01 ` Andrew Morton
2025-09-08 4:30 ` syzbot
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=1ebd15f2-b709-483b-ac52-2aa0e963454f@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1ab243d3eebb2aabf4a4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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