Re: [syzbot] [mm?] general protection fault in workingset_refault

[Yu Zhao <yuzhao@google.com>]

On Sun, Dec 22, 2024 at 3:44 AM syzbot
<syzbot+d21d8cd32443d6fbded1@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    8faabc041a00 Merge tag 'net-6.13-rc4' of git://git.kernel...
> git tree:       upstream

This is the mainline.

> console output: https://syzkaller.appspot.com/x/log.txt?x=10f39cf8580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769
> dashboard link: https://syzkaller.appspot.com/bug?extid=d21d8cd32443d6fbded1
> 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/0bdb6cecaf61/disk-8faabc04.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/98b22dfadac0/vmlinux-8faabc04.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/65a511d3ba7f/bzImage-8faabc04.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d21d8cd32443d6fbded1@syzkaller.appspotmail.com
>
> Oops: general protection fault, probably for non-canonical address 0xdffffc0000000998: 0000 [#1] PREEMPT SMP KASAN PTI
> KASAN: probably user-memory-access in range [0x0000000000004cc0-0x0000000000004cc7]
> CPU: 1 UID: 0 PID: 6298 Comm: syz.0.89 Not tainted 6.13.0-rc3-syzkaller-00136-g8faabc041a00 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
> RIP: 0010:mem_cgroup_lruvec include/linux/memcontrol.h:707 [inline]
> RIP: 0010:lru_gen_test_recent mm/workingset.c:274 [inline]
> RIP: 0010:lru_gen_refault mm/workingset.c:293 [inline]
> RIP: 0010:workingset_refault+0x234/0x1390 mm/workingset.c:548

So it can' be related to the recent changes in mm-unstable [1]. But I
keep an eye on it regardless.

[1] https://lore.kernel.org/20241207221522.2250311-1-yuzhao@google.com/