mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [syzbot] [block?] BUG: sleeping function called from invalid context in null_insert_page
@ 2026-09-04 22:23 syzbot
  2026-09-09 21:35 ` syzbot
  0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2026-09-04 22:23 UTC (permalink / raw)
  To: linux-block, linux-kernel, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    f1b8fa82cab7 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=17b7e779580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d1128bc53f2ef7f3
dashboard link: https://syzkaller.appspot.com/bug?extid=95fdab36405e5ffdb680
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/932d85a2bda2/disk-f1b8fa82.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5b6b8fb76e8d/vmlinux-f1b8fa82.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c246b61ee396/Image-f1b8fa82.gz.xz

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

BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:323
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 8414, name: syz.7.670
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
1 lock held by syz.7.670/8414:
 #0: ffff800088d271a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffff800088d271a0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffff800088d271a0 (rcu_read_lock){....}-{1:3}, at: blk_mq_dispatch_queue_requests+0x110/0x6d4 block/blk-mq.c:2872
CPU: 0 UID: 0 PID: 8414 Comm: syz.7.670 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/07/2026
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 __might_resched+0x354/0x4c0 kernel/sched/core.c:9197
 __might_sleep+0x84/0xdc kernel/sched/core.c:9126
 might_alloc include/linux/sched/mm.h:323 [inline]
 slab_pre_alloc_hook mm/slub.c:4537 [inline]
 slab_alloc_node mm/slub.c:4897 [inline]
 __kmalloc_cache_noprof+0x88/0x5ec mm/slub.c:5485
 _kmalloc_noprof include/linux/slab.h:988 [inline]
 null_alloc_page drivers/block/null_blk/main.c:870 [inline]
 null_insert_page+0x94/0x4e8 drivers/block/null_blk/main.c:1019
 copy_to_nullb drivers/block/null_blk/main.c:1157 [inline]
 null_transfer drivers/block/null_blk/main.c:1271 [inline]
 null_handle_data_transfer drivers/block/null_blk/main.c:1300 [inline]
 null_handle_memory_backed+0x474/0x9d8 drivers/block/null_blk/main.c:1380
 null_process_cmd+0x118/0x1b0 drivers/block/null_blk/main.c:1434
 null_handle_cmd drivers/block/null_blk/main.c:1457 [inline]
 null_queue_rq+0x788/0xa88 drivers/block/null_blk/main.c:1703
 null_queue_rqs+0x108/0x204 drivers/block/null_blk/main.c:1717
 __blk_mq_flush_list block/blk-mq.c:2827 [inline]
 blk_mq_dispatch_queue_requests+0x33c/0x6d4 block/blk-mq.c:2872
 blk_mq_flush_plug_list+0x37c/0x494 block/blk-mq.c:2960
 __blk_flush_plug+0x364/0x440 block/blk-core.c:1266
 blk_finish_plug+0x68/0x90 block/blk-core.c:1293
 blkdev_writepages+0x128/0x184 block/fops.c:486
 do_writepages+0x284/0x47c mm/page-writeback.c:2571
 filemap_writeback+0x230/0x2bc mm/filemap.c:387
 filemap_fdatawrite_range mm/filemap.c:412 [inline]
 filemap_write_and_wait_range+0x90/0x114 mm/filemap.c:684
 filemap_write_and_wait include/linux/pagemap.h:65 [inline]
 sync_blockdev block/bdev.c:276 [inline]
 bdev_release+0x114/0x328 block/bdev.c:1129
 blkdev_release+0x20/0x34 block/fops.c:680
 __fput+0x338/0x74c fs/file_table.c:512
 fput_close_sync+0x10c/0x278 fs/file_table.c:617
 __do_sys_close fs/open.c:1511 [inline]
 __se_sys_close fs/open.c:1496 [inline]
 __arm64_sys_close+0x80/0x110 fs/open.c:1496
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:758
 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:777
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:590


---
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 syzkaller@googlegroups.com.

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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [syzbot] [block?] BUG: sleeping function called from invalid context in null_insert_page
  2026-09-04 22:23 [syzbot] [block?] BUG: sleeping function called from invalid context in null_insert_page syzbot
@ 2026-09-09 21:35 ` syzbot
  0 siblings, 0 replies; 2+ messages in thread
From: syzbot @ 2026-09-09 21:35 UTC (permalink / raw)
  To: linux-block, linux-kernel, syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    893e11787f78 Merge tag 'x86_urgent_for_7.3-rc3' of git://g..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17e50925580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=95fdab36405e5ffdb680
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10c13749580000

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

null_blk: disk syzdev created
BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:322
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 6031, name: syz-executor254
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
locks held by syz-executor254/6031: 1, last CPU#0:
 #0: ffffffff8edec2e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #0: ffffffff8edec2e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8edec2e0 (rcu_read_lock){....}-{1:3}, at: blk_mq_dispatch_queue_requests+0x148/0x7c0 block/blk-mq.c:2872
CPU: 0 UID: 0 PID: 6031 Comm: syz-executor254 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 __might_resched.cold+0x1dc/0x222 kernel/sched/core.c:9256
 might_alloc include/linux/sched/mm.h:322 [inline]
 slab_pre_alloc_hook mm/slub.c:4636 [inline]
 slab_alloc_node mm/slub.c:4974 [inline]
 __kmalloc_cache_noprof+0x3e3/0x6d0 mm/slub.c:5559
 _kmalloc_noprof include/linux/slab.h:991 [inline]
 null_alloc_page drivers/block/null_blk/main.c:878 [inline]
 null_insert_page+0x10b/0x6c0 drivers/block/null_blk/main.c:1027
 copy_to_nullb drivers/block/null_blk/main.c:1165 [inline]
 null_transfer drivers/block/null_blk/main.c:1279 [inline]
 null_handle_data_transfer+0x7df/0xe20 drivers/block/null_blk/main.c:1308
 null_handle_memory_backed drivers/block/null_blk/main.c:1388 [inline]
 null_process_cmd+0x1e3/0x290 drivers/block/null_blk/main.c:1442
 null_handle_cmd drivers/block/null_blk/main.c:1465 [inline]
 null_queue_rq+0x8e4/0xfb0 drivers/block/null_blk/main.c:1711
 null_queue_rqs+0xe9/0x2f0 drivers/block/null_blk/main.c:1725
 __blk_mq_flush_list block/blk-mq.c:2827 [inline]
 __blk_mq_flush_list+0x9a/0xc0 block/blk-mq.c:2823
 blk_mq_dispatch_queue_requests+0x184/0x7c0 block/blk-mq.c:2872
 blk_mq_flush_plug_list+0x1f2/0x600 block/blk-mq.c:2960
 __blk_flush_plug+0x2c4/0x4b0 block/blk-core.c:1270
 blk_finish_plug+0x5c/0xa0 block/blk-core.c:1297
 blkdev_writepages+0xf6/0x150 block/fops.c:488
 do_writepages+0x278/0x600 mm/page-writeback.c:2560
 filemap_writeback+0x22d/0x2e0 mm/filemap.c:387
 filemap_fdatawrite_range mm/filemap.c:412 [inline]
 file_write_and_wait_range+0xcd/0x140 mm/filemap.c:786
 blkdev_fsync+0x6c/0xd0 block/fops.c:596
 vfs_fsync_range fs/sync.c:186 [inline]
 vfs_fsync fs/sync.c:200 [inline]
 do_fsync+0xbf/0x220 fs/sync.c:211
 __do_sys_fsync fs/sync.c:216 [inline]
 __se_sys_fsync fs/sync.c:214 [inline]
 __x64_sys_fsync+0x32/0x50 fs/sync.c:214
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f756122f3b7
Code: 48 89 fa 4c 89 df e8 98 1d 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007fffc74cf400 EFLAGS: 00000202 ORIG_RAX: 000000000000004a
RAX: ffffffffffffffda RBX: 0000555566674400 RCX: 00007f756122f3b7
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 000000000000000a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00007f756126bae3
R13: 00007fffc74cf450 R14: 00007f7561268060 R15: 00007f7561268140
 </TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-09-09 21:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-04 22:23 [syzbot] [block?] BUG: sleeping function called from invalid context in null_insert_page syzbot
2026-09-09 21:35 ` syzbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®