From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+b253ade8e1751d90a7a9@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in bio_iov_iter_get_pages
Date: Sun, 7 Sep 2025 16:19:36 +0800 [thread overview]
Message-ID: <20250907081937.6583-1-hdanton@sina.com> (raw)
In-Reply-To: <68bd3027.050a0220.192772.01cc.GAE@google.com>
> Date: Sun, 07 Sep 2025 00:11:35 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: be5d4872e528 Add linux-next specific files for 20250905
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17896962580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a726684450a7d788
> dashboard link: https://syzkaller.appspot.com/bug?extid=b253ade8e1751d90a7a9
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10496962580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a98962580000
#syz test
--- x/mm/gup.c
+++ y/mm/gup.c
@@ -2981,6 +2981,7 @@ static int gup_fast_pmd_leaf(pmd_t orig,
return 0;
}
+ pages += *nr;
*nr += refs;
for (; refs; refs--)
*(pages++) = page++;
@@ -3024,6 +3025,7 @@ static int gup_fast_pud_leaf(pud_t orig,
return 0;
}
+ pages += *nr;
*nr += refs;
for (; refs; refs--)
*(pages++) = page++;
--
next prev parent reply other threads:[~2025-09-07 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 7:11 syzbot
2025-09-07 8:19 ` Hillf Danton [this message]
2025-09-07 9:32 ` 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=20250907081937.6583-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+b253ade8e1751d90a7a9@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