* Re: [syzbot] [erofs?] WARNING: CPU: NUM PID: NUM at mm/page_alloc.c:LINE get_page_from_freeli
@ 2023-01-05 11:14 ` Aleksandr Nogikh
0 siblings, 0 replies; 7+ messages in thread
From: Aleksandr Nogikh @ 2023-01-05 11:14 UTC (permalink / raw)
To: Xiang Gao
Cc: syzbot, akpm, chao, linux-erofs, linux-kernel, syzkaller-bugs,
xiang
Hi,
On Thu, Jan 5, 2023 at 11:54 AM Xiang Gao <hsiangkao@linux.alibaba.com> wrote:
> I wasn't able to build the kernel with this kernel config, it shows:
> "...
> FATAL: modpost: vmlinux.o is truncated. sechdrs[i].sh_offset=1399394064 > sizeof(*hrd)=64
> make[2]: *** [Module.symvers] Error 1
> make[1]: *** [modpost] Error 2
> make: *** [__sub-make] Error 2
> "
Could you please tell, what exact compiler/linker version did you use?
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/0c8a5f06ceb3/disk-f9ff5644.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/be222e852ae2/vmlinux-f9ff5644.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/d9f42a53b05e/bzImage-f9ff5644.xz
>
> Finally I tried the original kernel image, and it printed some other
> random bug when booting system and then reboot, like:
>
> [ 36.991123][ T1] ==================================================================
> [ 36.991800][ T1] BUG: KASAN: slab-out-of-bounds in copy_array+0x96/0x100
> [ 36.992438][ T1] Write of size 32 at addr ffff888018c34640 by task systemd/1
< .. >
Interesting!
I've just tried to boot it with qemu and it was fine.
qemu-system-x86_64 -smp 2,sockets=2,cores=1 -m 4G -drive
file=disk-f9ff5644.raw,format=raw -snapshot -nographic -enable-kvm
So it looks like it's some difference between these VMMs that causes
that bug to fire.
>
> May I ask it can be reproducable on the latest -rc kernel?
We can ask syzbot about v6.2-rc2:
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
88603b6dc419445847923fcb7fe5080067a30f98
>
> Thanks,
> Gao Xiang
>
--
Aleksandr
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [syzbot] [erofs?] WARNING: CPU: NUM PID: NUM at mm/page_alloc.c:LINE get_page_from_freeli
2023-01-05 11:14 ` Aleksandr Nogikh
(?)
@ 2023-01-05 14:33 ` syzbot
-1 siblings, 0 replies; 7+ messages in thread
From: syzbot @ 2023-01-05 14:33 UTC (permalink / raw)
To: akpm, chao, hsiangkao, linux-erofs, linux-kernel, nogikh,
syzkaller-bugs, xiang
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in get_page_from_freelist
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4385 at mm/page_alloc.c:3829 rmqueue mm/page_alloc.c:3829 [inline]
WARNING: CPU: 1 PID: 4385 at mm/page_alloc.c:3829 get_page_from_freelist+0xbf3/0x2ce0 mm/page_alloc.c:4280
Modules linked in:
CPU: 1 PID: 4385 Comm: kworker/u5:1 Not tainted 6.2.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: erofs_unzipd z_erofs_decompressqueue_work
RIP: 0010:rmqueue mm/page_alloc.c:3829 [inline]
RIP: 0010:get_page_from_freelist+0xbf3/0x2ce0 mm/page_alloc.c:4280
Code: 48 c1 e8 03 42 80 3c 28 00 0f 85 18 1f 00 00 48 8b 03 f7 84 24 d8 00 00 00 00 80 00 00 48 89 44 24 68 74 08 41 83 fe 01 76 02 <0f> 0b 41 83 fe 09 0f 94 c2 41 83 fe 03 0f 96 c0 08 c2 88 54 24 50
RSP: 0018:ffffc900055e74d8 EFLAGS: 00010202
RAX: ffff88813fffae00 RBX: ffff88813fffc300 RCX: ffff88813fffabe8
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffc900055e7718
RBP: 0000000000000002 R08: 0000000000002b49 R09: 0000000000078534
R10: 0000000000002b48 R11: 0000000000000000 R12: 0000000000002b48
R13: dffffc0000000000 R14: 0000000000000009 R15: ffff88813fffa700
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff496515829 CR3: 000000000c48e000 CR4: 0000000000350ee0
Call Trace:
<TASK>
__alloc_pages+0x1cb/0x5b0 mm/page_alloc.c:5549
alloc_pages+0x1aa/0x270 mm/mempolicy.c:2286
vm_area_alloc_pages mm/vmalloc.c:2989 [inline]
__vmalloc_area_node mm/vmalloc.c:3057 [inline]
__vmalloc_node_range+0x978/0x13c0 mm/vmalloc.c:3227
kvmalloc_node+0x156/0x1a0 mm/util.c:606
kvmalloc include/linux/slab.h:737 [inline]
kvmalloc_array include/linux/slab.h:755 [inline]
kvcalloc include/linux/slab.h:760 [inline]
z_erofs_decompress_pcluster fs/erofs/zdata.c:1035 [inline]
z_erofs_decompress_queue+0x6e2/0x3060 fs/erofs/zdata.c:1141
z_erofs_decompressqueue_work+0x77/0xb0 fs/erofs/zdata.c:1153
process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
worker_thread+0x669/0x1090 kernel/workqueue.c:2436
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Tested on:
commit: 88603b6d Linux 6.2-rc2
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1193edc6480000
kernel config: https://syzkaller.appspot.com/x/.config?x=46221e8203c7aca6
dashboard link: https://syzkaller.appspot.com/bug?extid=c3729cda01706a04fb98
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [syzbot] [erofs?] WARNING: CPU: NUM PID: NUM at mm/page_alloc.c:LINE get_page_from_freeli
2023-01-05 11:14 ` Aleksandr Nogikh
@ 2023-01-05 15:59 ` Xiang Gao
-1 siblings, 0 replies; 7+ messages in thread
From: Xiang Gao @ 2023-01-05 15:59 UTC (permalink / raw)
To: Aleksandr Nogikh; +Cc: syzkaller-bugs, linux-kernel, akpm, linux-erofs, syzbot
Hi Aleksandr,
On 2023/1/5 19:14, Aleksandr Nogikh wrote:
> Hi,
>
> On Thu, Jan 5, 2023 at 11:54 AM Xiang Gao <hsiangkao@linux.alibaba.com> wrote:
>
>> I wasn't able to build the kernel with this kernel config, it shows:
>> "...
>> FATAL: modpost: vmlinux.o is truncated. sechdrs[i].sh_offset=1399394064 > sizeof(*hrd)=64
>> make[2]: *** [Module.symvers] Error 1
>> make[1]: *** [modpost] Error 2
>> make: *** [__sub-make] Error 2
>> "
>
> Could you please tell, what exact compiler/linker version did you use?
Thanks for your help.
GCC 9.2.1 on my developping server.
>
>
>>>
>>> Downloadable assets:
>>> disk image: https://storage.googleapis.com/syzbot-assets/0c8a5f06ceb3/disk-f9ff5644.raw.xz
>>> vmlinux: https://storage.googleapis.com/syzbot-assets/be222e852ae2/vmlinux-f9ff5644.xz
>>> kernel image: https://storage.googleapis.com/syzbot-assets/d9f42a53b05e/bzImage-f9ff5644.xz
>>
>> Finally I tried the original kernel image, and it printed some other
>> random bug when booting system and then reboot, like:
>>
>> [ 36.991123][ T1] ==================================================================
>> [ 36.991800][ T1] BUG: KASAN: slab-out-of-bounds in copy_array+0x96/0x100
>> [ 36.992438][ T1] Write of size 32 at addr ffff888018c34640 by task systemd/1
> < .. >
>
> Interesting!
> I've just tried to boot it with qemu and it was fine.
>
> qemu-system-x86_64 -smp 2,sockets=2,cores=1 -m 4G -drive
> file=disk-f9ff5644.raw,format=raw -snapshot -nographic -enable-kvm
>
> So it looks like it's some difference between these VMMs that causes
> that bug to fire.
I think the problem is that the rootfs which I used has more complicated
workload than the given one.
>
>>
>> May I ask it can be reproducable on the latest -rc kernel?
>
> We can ask syzbot about v6.2-rc2:
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> 88603b6dc419445847923fcb7fe5080067a30f98
I think I know the root cause: It seems that kvcalloc doesn't support
GFP_NOFAIL, I will use kcalloc directly instead.
Thanks,
Gao Xiang
>
>>
>> Thanks,
>> Gao Xiang
>>
>
> --
> Aleksandr
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [syzbot] [erofs?] WARNING: CPU: NUM PID: NUM at mm/page_alloc.c:LINE get_page_from_freeli
@ 2023-01-05 15:59 ` Xiang Gao
0 siblings, 0 replies; 7+ messages in thread
From: Xiang Gao @ 2023-01-05 15:59 UTC (permalink / raw)
To: Aleksandr Nogikh
Cc: syzbot, akpm, chao, linux-erofs, linux-kernel, syzkaller-bugs,
xiang
Hi Aleksandr,
On 2023/1/5 19:14, Aleksandr Nogikh wrote:
> Hi,
>
> On Thu, Jan 5, 2023 at 11:54 AM Xiang Gao <hsiangkao@linux.alibaba.com> wrote:
>
>> I wasn't able to build the kernel with this kernel config, it shows:
>> "...
>> FATAL: modpost: vmlinux.o is truncated. sechdrs[i].sh_offset=1399394064 > sizeof(*hrd)=64
>> make[2]: *** [Module.symvers] Error 1
>> make[1]: *** [modpost] Error 2
>> make: *** [__sub-make] Error 2
>> "
>
> Could you please tell, what exact compiler/linker version did you use?
Thanks for your help.
GCC 9.2.1 on my developping server.
>
>
>>>
>>> Downloadable assets:
>>> disk image: https://storage.googleapis.com/syzbot-assets/0c8a5f06ceb3/disk-f9ff5644.raw.xz
>>> vmlinux: https://storage.googleapis.com/syzbot-assets/be222e852ae2/vmlinux-f9ff5644.xz
>>> kernel image: https://storage.googleapis.com/syzbot-assets/d9f42a53b05e/bzImage-f9ff5644.xz
>>
>> Finally I tried the original kernel image, and it printed some other
>> random bug when booting system and then reboot, like:
>>
>> [ 36.991123][ T1] ==================================================================
>> [ 36.991800][ T1] BUG: KASAN: slab-out-of-bounds in copy_array+0x96/0x100
>> [ 36.992438][ T1] Write of size 32 at addr ffff888018c34640 by task systemd/1
> < .. >
>
> Interesting!
> I've just tried to boot it with qemu and it was fine.
>
> qemu-system-x86_64 -smp 2,sockets=2,cores=1 -m 4G -drive
> file=disk-f9ff5644.raw,format=raw -snapshot -nographic -enable-kvm
>
> So it looks like it's some difference between these VMMs that causes
> that bug to fire.
I think the problem is that the rootfs which I used has more complicated
workload than the given one.
>
>>
>> May I ask it can be reproducable on the latest -rc kernel?
>
> We can ask syzbot about v6.2-rc2:
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> 88603b6dc419445847923fcb7fe5080067a30f98
I think I know the root cause: It seems that kvcalloc doesn't support
GFP_NOFAIL, I will use kcalloc directly instead.
Thanks,
Gao Xiang
>
>>
>> Thanks,
>> Gao Xiang
>>
>
> --
> Aleksandr
^ permalink raw reply [flat|nested] 7+ messages in thread