From: Shakeel Butt <shakeel.butt@linux.dev>
To: syzbot <syzbot+5dd4e428fa723938e6fd@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, cgroups@vger.kernel.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, muchun.song@linux.dev,
roman.gushchin@linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [cgroups?] general protection fault in refill_obj_stock
Date: Tue, 27 May 2025 10:42:29 -0700 [thread overview]
Message-ID: <loiano2kji2pin44d7btrufm5ovdi5rm4fdmajhlvarsbfrbru@olcbsrrrdrh3> (raw)
In-Reply-To: <6835c01c.a70a0220.253bc2.00b7.GAE@google.com>
On Tue, May 27, 2025 at 06:37:32AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 914873bc7df9 Merge tag 'x86-build-2025-05-25' of git://git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12dcf882580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=231a962e5fdb804b
> dashboard link: https://syzkaller.appspot.com/bug?extid=5dd4e428fa723938e6fd
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/ecae640d0786/disk-914873bc.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/d451e50efeae/vmlinux-914873bc.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/8f7363263e49/bzImage-914873bc.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5dd4e428fa723938e6fd@syzkaller.appspotmail.com
#syz dup: [syzbot] [cgroups?] [mm?] BUG: unable to handle kernel paging request in percpu_ref_get_many (2)
prev parent reply other threads:[~2025-05-27 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 13:37 syzbot
2025-05-27 17:42 ` Shakeel Butt [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=loiano2kji2pin44d7btrufm5ovdi5rm4fdmajhlvarsbfrbru@olcbsrrrdrh3 \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=syzbot+5dd4e428fa723938e6fd@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