[v5.15] WARNING in __v9fs_get_acl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14fc8e14c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=353a11a1dbfe7820
dashboard link: https://syzkaller.appspot.com/bug?extid=099b12b91b0072764f65
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741458b6f24d/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46cdc0f15ae5/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15bf795c52fa/Image-bbf9f29b.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+099b12...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5115 at mm/page_alloc.c:5396 __alloc_pages+0x414/0x7a0 mm/page_alloc.c:5396
Modules linked in:
CPU: 0 PID: 5115 Comm: syz-executor.0 Not tainted 5.15.101-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x414/0x7a0 mm/page_alloc.c:5396
lr : __alloc_pages+0xc8/0x7a0 mm/page_alloc.c:5389
sp : ffff80001da376c0
x29: ffff80001da377b0 x28: ffff80001da376e0 x27: dfff800000000000
x26: ffff700003b46edc x25: 0000000000000000 x24: ffff80001da37700
x23: ffff800018506544 x22: 0000000000040d40 x21: ffff80001da37720
x20: 0000000000000000 x19: 0000000000000014 x18: 0000000000000000
x17: ff808000088a4f6c x16: 0000000000000002 x15: ffff8000088a4f6c
x14: 0000000000000005 x13: ffffffffffffffff x12: 0000000000000005
x11: 1ffff00003b46ee4 x10: 0000000000000000 x9 : 0000000000000000
x8 : ffff80001da37748 x7 : 0000000000000000 x6 : ffff80000805dbbc
x5 : ffff0000d1ead588 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff80001da37720
Call trace:
__alloc_pages+0x414/0x7a0 mm/page_alloc.c:5396
alloc_pages+0x390/0x634
kmalloc_order+0x40/0x154 mm/slab_common.c:966
kmalloc_order_trace+0x30/0x28c mm/slab_common.c:982
kmalloc_large include/linux/slab.h:520 [inline]
__kmalloc+0x32c/0x404 mm/slub.c:4396
kmalloc include/linux/slab.h:596 [inline]
kzalloc include/linux/slab.h:721 [inline]
__v9fs_get_acl+0x58/0x150 fs/9p/acl.c:36
v9fs_get_acl+0xb8/0x2f0 fs/9p/acl.c:71
v9fs_mount+0x604/0x780 fs/9p/vfs_super.c:184
legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
vfs_get_tree+0x90/0x274 fs/super.c:1499
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584
irq event stamp: 1398
hardirqs last enabled at (1397): [<ffff8000088d2d9c>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (1398): [<ffff800011a047b0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (980): [<ffff800008775030>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (980): [<ffff800008775030>] bdi_register_va+0x51c/0x9bc mm/backing-dev.c:896
softirqs last disabled at (978): [<ffff800008774e18>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (978): [<ffff800008774e18>] bdi_register_va+0x304/0x9bc mm/backing-dev.c:886
---[ end trace 44a4c17030cd917b ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=17475494c80000

kernel config: https://syzkaller.appspot.com/x/.config?x=353a11a1dbfe7820
dashboard link: https://syzkaller.appspot.com/bug?extid=099b12b91b0072764f65
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f3ebf4c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16df6f66c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741458b6f24d/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46cdc0f15ae5/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15bf795c52fa/Image-bbf9f29b.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+099b12...@syzkaller.appspotmail.com

------------[ cut here ]------------

WARNING: CPU: 0 PID: 4059 at mm/page_alloc.c:5396 __alloc_pages+0x414/0x7a0 mm/page_alloc.c:5396
Modules linked in:
CPU: 0 PID: 4059 Comm: syz-executor392 Not tainted 5.15.101-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x414/0x7a0 mm/page_alloc.c:5396
lr : __alloc_pages+0xc8/0x7a0 mm/page_alloc.c:5389

sp : ffff80001ca976c0
x29: ffff80001ca977b0 x28: ffff80001ca976e0 x27: dfff800000000000
x26: ffff700003952edc x25: 0000000000000000 x24: ffff80001ca97700
x23: ffff800018506544 x22: 0000000000040d40 x21: ffff80001ca97720

x20: 0000000000000000 x19: 0000000000000014 x18: 0000000000000000

x17: ff808000088a4f6c x16: 0000000000000000 x15: ffff8000088a4f6c

x14: 0000000000000005 x13: ffffffffffffffff x12: 0000000000000005

x11: 1ffff00003952ee4 x10: 0000000000000000 x9 : 0000000000000000
x8 : ffff80001ca97748 x7 : 0000000000000000 x6 : ffff80000805dbbc
x5 : ffff0000cddbb9c8 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff80001ca97720

irq event stamp: 14830
hardirqs last enabled at (14829): [<ffff8000088d2d9c>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (14830): [<ffff800011a047b0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (14420): [<ffff800008775030>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (14420): [<ffff800008775030>] bdi_register_va+0x51c/0x9bc mm/backing-dev.c:896
softirqs last disabled at (14418): [<ffff800008774e18>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (14418): [<ffff800008774e18>] bdi_register_va+0x304/0x9bc mm/backing-dev.c:886
---[ end trace a2f0ddb9e546e0e5 ]---

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1cc3fcf63192 Linux 6.1.18
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=120bebf4c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=157296d36f92ea19
dashboard link: https://syzkaller.appspot.com/bug?extid=a2c0ccf6ce88f46ee379

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1147a656c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12694684c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e4c0d43698b/disk-1cc3fcf6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a4de39d735de/vmlinux-1cc3fcf6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/82bab928f6e3/Image-1cc3fcf6.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+a2c0cc...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4306 at mm/page_alloc.c:5534 __alloc_pages+0x418/0x87c mm/page_alloc.c:5534
Modules linked in:
CPU: 0 PID: 4306 Comm: syz-executor118 Not tainted 6.1.18-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : __alloc_pages+0x418/0x87c mm/page_alloc.c:5534
lr : __alloc_pages+0xc8/0x87c mm/page_alloc.c:5528
sp : ffff80001db27760
x29: ffff80001db27850 x28: ffff80001db27780 x27: dfff800000000000
x26: ffff700003b64ef0 x25: 0000000000000000 x24: ffff80001db277a0
x23: 0000000000000000 x22: 0000000000040d40 x21: ffff80001db277c0
x20: 1ffff00003b64ef4 x19: 0000000000000014 x18: 1fffe000368b0376
x17: ffff80001572d000 x16: ffff8000121a26c0 x15: ffff800008ad6924
x14: ffff800008ad36c8 x13: ffff800008063160 x12: 0000000000000005
x11: 1ffff00003b64ef8 x10: 0000000000000000 x9 : 0000000000000001
x8 : ffff800018053000 x7 : 0000000000000000 x6 : ffff800008063160
x5 : ffff0000c7bbf9a8 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff80001db277c0
Call trace:
__alloc_pages+0x418/0x87c mm/page_alloc.c:5534
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0xbc/0x21c mm/slab_common.c:1096
__do_kmalloc_node mm/slab_common.c:943 [inline]
__kmalloc+0x130/0x1c4 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
kzalloc include/linux/slab.h:689 [inline]
__v9fs_get_acl+0x58/0x150 fs/9p/acl.c:28
v9fs_get_acl+0xb8/0x2c8 fs/9p/acl.c:63
v9fs_mount+0x77c/0xa5c fs/9p/vfs_super.c:184
legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
vfs_get_tree+0x90/0x274 fs/super.c:1544
do_new_mount+0x25c/0x8c8 fs/namespace.c:3040
path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
irq event stamp: 16366
hardirqs last enabled at (16365): [<ffff80000897d020>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:242
hardirqs last disabled at (16366): [<ffff80001224fb14>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (16152): [<ffff8000088043dc>] spin_unlock_bh include/linux/spinlock.h:395 [inline]
softirqs last enabled at (16152): [<ffff8000088043dc>] bdi_register_va+0x518/0xa3c mm/backing-dev.c:889
softirqs last disabled at (16150): [<ffff8000088041c4>] spin_lock_bh include/linux/spinlock.h:355 [inline]
softirqs last disabled at (16150): [<ffff8000088041c4>] bdi_register_va+0x300/0xa3c mm/backing-dev.c:879
---[ end trace 0000000000000000 ]---

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches