linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6792

Status: fixed on 2020/07/17 17:58
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com
Fix commit: 811985365378 ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr
First crash: 2255d, last: 2255d
▶ ▼ Duplicate bugs (18)
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream test error: BUG: using smp_processor_id() in preemptible code in ext4_ext_map_blocks ext4 -1 3 2245d 2247d 0/29 closed as dup on 2020/06/10 12:54
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/41 ext4 -1 1 2254d 2250d 0/29 closed as dup on 2020/06/07 14:21
net-next test error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks ext4 -1 110 2240d 2244d 0/29 closed as dup on 2020/06/13 00:43
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/4205 ext4 -1 1 2254d 2250d 0/29 closed as dup on 2020/06/07 14:22
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: systemd-rfkill/6731 ext4 -1 1 2255d 2255d 0/29 closed as dup on 2020/06/05 04:13
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6793 ext4 -1 1 2254d 2250d 0/29 closed as dup on 2020/06/07 14:23
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/6740 ext4 -1 1 2255d 2255d 0/29 closed as dup on 2020/06/05 04:13
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: systemd-rfkill/6910 ext4 -1 1 2254d 2250d 0/29 closed as dup on 2020/06/07 14:15
net test error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks ext4 -1 178 2240d 2244d 0/29 closed as dup on 2020/06/13 00:43
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/198 ext4 -1 1 2254d 2250d 0/29 closed as dup on 2020/06/07 14:25
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: systemd-rfkill/6726 ext4 -1 1 2255d 2255d 0/29 closed as dup on 2020/06/05 04:13
net boot error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks ext4 -1 2 2241d 2244d 0/29 closed as dup on 2020/06/13 04:27
linux-next test error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks ext4 -1 92 2244d 2250d 0/29 closed as dup on 2020/06/07 23:13
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6927 ext4 -1 1 2255d 2255d 0/29 closed as dup on 2020/06/05 04:13
upstream test error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks ext4 -1 1478 2241d 2247d 0/29 closed as dup on 2020/06/10 07:17
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/46 ext4 -1 1 2255d 2255d 0/29 closed as dup on 2020/06/05 04:12
upstream test error: BUG: using smp_processor_id() in preemptible code in corrupted -1 9 2241d 2246d 0/29 closed as dup on 2020/06/11 11:06
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: systemd-rfkill/6728 ext4 -1 1 2254d 2252d 0/29 closed as dup on 2020/06/05 04:12
▶ ▼ Discussions (5)
Title Replies (including bot) Last reply
linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6792 4 (6) 2020/06/12 13:51
[PATCHv2 1/1] ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr 4 (4) 2020/06/11 15:03
Re: [PATCHv2 1/1] ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr 1 (1) 2020/06/10 02:06
[PATCHv5 1/1] ext4: mballoc: Use raw_cpu_ptr instead of this_cpu_ptr 5 (5) 2020/06/09 10:57
Re: linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6792 1 (1) 2020/06/03 10:06

Sample crash report:
BUG: using smp_processor_id() in preemptible [00000000] code: syz-fuzzer/6792
caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
CPU: 1 PID: 6792 Comm: syz-fuzzer Not tainted 5.7.0-next-20200602-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x18f/0x20d lib/dump_stack.c:118
 check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
 ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
 ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
 ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
 ext4_getblk+0xad/0x520 fs/ext4/inode.c:833
 ext4_bread+0x7c/0x380 fs/ext4/inode.c:883
 ext4_append+0x153/0x360 fs/ext4/namei.c:67
 ext4_init_new_dir fs/ext4/namei.c:2757 [inline]
 ext4_mkdir+0x5e0/0xdf0 fs/ext4/namei.c:2802
 vfs_mkdir+0x419/0x690 fs/namei.c:3632
 do_mkdirat+0x21e/0x280 fs/namei.c:3655
 do_syscall_64+0x60/0xe0 arch/x86/entry/common.c:359
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4b02a0
Code: Bad RIP value.
RSP: 002b:000000c00010d4b8 EFLAGS: 00000212 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 000000c00002c000 RCX: 00000000004b02a0
RDX: 00000000000001c0 RSI: 000000c000026b40 RDI: ffffffffffffff9c
RBP: 000000c00010d510 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: ffffffffffffffff
R13: 000000000000005b R14: 000000000000005a R15: 0000000000000100

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/06/02 11:04 linux-next 0e21d4620dd0 a0331e89 .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.