syzbot


BUG: sleeping function called from invalid context in corrupted (2)

Status: auto-obsoleted due to no activity on 2023/04/21 20:05
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+efe1afd49d981d281ae4@syzkaller.appspotmail.com
First crash: 736d, last: 735d
Cause bisection: introduced by (bisect log) :
commit d8616ee2affcff37c5d315310da557a694a3303d
Author: Wang Yufen <wangyufen@huawei.com>
Date: Tue May 24 07:53:11 2022 +0000

  bpf, sockmap: Fix sk->sk_forward_alloc warn_on in sk_stream_kill_queues

Crash: BUG: sleeping function called from invalid context in sock_map_destroy (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] BUG: sleeping function called from invalid context in corrupted (2) 1 (2) 2022/06/09 10:26
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: sleeping function called from invalid context in corrupted C done 2 1298d 1299d 1/1 fixed on 2020/12/25 08:46
upstream BUG: sleeping function called from invalid context in corrupted wireless syz done 18 1289d 1313d 19/27 fixed on 2021/03/10 01:49
Last patch testing requests (6)
Created Duration User Patch Repo Result
2023/04/21 19:36 28m retest repro linux-next OK log
2022/11/24 21:30 19m retest repro linux-next OK log
2022/11/24 16:30 19m retest repro linux-next OK log
2022/11/24 04:30 20m retest repro linux-next OK log
2022/11/24 03:30 22m retest repro linux-next error OK
2022/06/11 02:53 17m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 03c312cc5f47 OK log

Sample crash report:
BUG: sleeping function called from invalid context at kernel/workqueue.c:3010
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 3612, name: syz-executor806
preempt_count: 201, expected: 0
RCU nest depth: 0, expected: 0
3 locks held by syz-executor806/3612:
 #0: ffff888072661410 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:740 [inline]
 #0: ffff888072661410 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x280 net/socket.c:649
 #1: ffff888026a11ab0 (sk_lock-AF_INET6){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1691 [inline]
 #1: ffff888026a11ab0 (sk_lock-AF_INET6){+.+.}-{0:0}, at: tcp_close+0x1e/0xc0 net/ipv4/tcp.c:2908
 #2: ffff888026a11a30 (slock-AF_INET6){+...}-{2:2}, at: spin_lock include/linux/spinlock.h:360 [inline]
 #2: ffff888026a11a30 (slock-AF_INET6){+...}-{2:2}, at: __tcp_close+0x722/0x12b0 net/ipv4/tcp.c:2830
Preemption disabled at:
[<ffffffff87ddddca>] local_bh_disable include/linux/bottom_half.h:20 [inline]
[<ffffffff87ddddca>] __tcp_close+0x71a/0x12b0 net/ipv4/tcp.c:2829
CPU: 0 PID: 3612 Comm: syz-executor806 Not tainted 5.19.0-rc1-next-20220609-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 __might_resched.cold+0x222/0x26b kernel/sched/core.c:9823
 __flush_wor

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/06/09 18:59 linux-next ff539ac73ea5 0d5abf15 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root BUG: sleeping function called from invalid context in corrupted
2022/06/09 11:25 linux-next ff539ac73ea5 0d5abf15 .config console log report syz C ci-upstream-linux-next-kasan-gce-root BUG: sleeping function called from invalid context in corrupted
2022/06/09 11:05 linux-next ff539ac73ea5 0d5abf15 .config console log report syz C ci-upstream-linux-next-kasan-gce-root BUG: sleeping function called from invalid context in corrupted
2022/06/08 20:35 linux-next 03c312cc5f47 b2706118 .config console log report syz C ci-upstream-linux-next-kasan-gce-root BUG: sleeping function called from invalid context in corrupted
* Struck through repros no longer work on HEAD.