squashfs: SQUASHFS error: unable to read inode lookup table
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
======================================================
WARNING: possible circular locking dependency detected
4.14.292-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.1/10917 is trying to acquire lock:
((&strp->work)){+.+.}, at: [<ffffffff81367998>] flush_work+0x88/0x770 kernel/workqueue.c:2887
but task is already holding lock:
(sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] lock_sock include/net/sock.h:1473 [inline]
(sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_attach net/kcm/kcmsock.c:1390 [inline]
(sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_attach_ioctl net/kcm/kcmsock.c:1490 [inline]
(sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_ioctl+0x328/0xfb0 net/kcm/kcmsock.c:1701
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (sk_lock-AF_INET){+.+.}:
lock_sock_nested+0xb7/0x100 net/core/sock.c:2813
do_strp_work net/strparser/strparser.c:415 [inline]
strp_work+0x3e/0x100 net/strparser/strparser.c:434
process_one_work+0x793/0x14a0 kernel/workqueue.c:2117
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
-> #0 ((&strp->work)){+.+.}:
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
flush_work+0xad/0x770 kernel/workqueue.c:2890
__cancel_work_timer+0x321/0x460 kernel/workqueue.c:2965
strp_done+0x53/0xd0 net/strparser/strparser.c:519
kcm_attach net/kcm/kcmsock.c:1429 [inline]
kcm_attach_ioctl net/kcm/kcmsock.c:1490 [inline]
kcm_ioctl+0x828/0xfb0 net/kcm/kcmsock.c:1701
sock_do_ioctl net/socket.c:974 [inline]
sock_ioctl+0x2cc/0x4c0 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(sk_lock-AF_INET);
lock((&strp->work));
lock(sk_lock-AF_INET);
lock((&strp->work));
*** DEADLOCK ***
1 lock held by syz-executor.1/10917:
#0: (sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] lock_sock include/net/sock.h:1473 [inline]
#0: (sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_attach net/kcm/kcmsock.c:1390 [inline]
#0: (sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_attach_ioctl net/kcm/kcmsock.c:1490 [inline]
#0: (sk_lock-AF_INET){+.+.}, at: [<ffffffff86819888>] kcm_ioctl+0x328/0xfb0 net/kcm/kcmsock.c:1701
stack backtrace:
CPU: 0 PID: 10917 Comm: syz-executor.1 Not tainted 4.14.292-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
check_prev_add kernel/locking/lockdep.c:1905 [inline]
check_prevs_add kernel/locking/lockdep.c:2022 [inline]
validate_chain kernel/locking/lockdep.c:2464 [inline]
__lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
flush_work+0xad/0x770 kernel/workqueue.c:2890
__cancel_work_timer+0x321/0x460 kernel/workqueue.c:2965
strp_done+0x53/0xd0 net/strparser/strparser.c:519
kcm_attach net/kcm/kcmsock.c:1429 [inline]
kcm_attach_ioctl net/kcm/kcmsock.c:1490 [inline]
kcm_ioctl+0x828/0xfb0 net/kcm/kcmsock.c:1701
sock_do_ioctl net/socket.c:974 [inline]
sock_ioctl+0x2cc/0x4c0 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fec7d83e3c9
RSP: 002b:00007fec7c1b3168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fec7d950f80 RCX: 00007fec7d83e3c9
RDX: 0000000020000500 RSI: 00000000000089e0 RDI: 0000000000000003
RBP: 00007fec7d89933f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc7676fe7f R14: 00007fec7c1b3300 R15: 0000000000022000
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
qnx6: invalid mount options.
ntfs: (device loop3): parse_options(): Unrecognized mount option 00000000000000000000.
Cannot find add_set index 0 as target
cannot load conntrack support for proto=2
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
syz-executor.2 (10979) used greatest stack depth: 24552 bytes left
cannot load conntrack support for proto=2
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
kauditd_printk_skb: 7 callbacks suppressed
audit: type=1800 audit(1663014844.501:26): pid=11100 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14101 res=0
audit: type=1800 audit(1663014844.541:27): pid=11106 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="bus" dev="sda1" ino=14106 res=0
audit: type=1800 audit(1663014846.561:28): pid=11163 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file1" dev="sda1" ino=14113 res=0
audit: type=1800 audit(1663014849.552:29): pid=11195 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file1" dev="sda1" ino=14123 res=0
EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs error (device loop4): ext4_readdir:240: inode #2: block 16: comm syz-executor.4: path /root/syzkaller-testdir1357564328/syzkaller.NKnMmD/37/file0: bad entry in directory: directory entry overrun - offset=24, inode=11, rec_len=63764, name_len=0, size=1024
unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1
audit: type=1800 audit(1663014850.212:30): pid=11240 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file1" dev="sda1" ino=14094 res=0
audit: type=1800 audit(1663014850.562:31): pid=11262 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file1" dev="sda1" ino=14112 res=0
F2FS-fs (loop4): Unable to read 1th superblock
F2FS-fs (loop4): Unable to read 2th superblock
F2FS-fs (loop4): Unable to read 2th superblock
FAT-fs (loop1): Unrecognized mount option "" or missing value
F2FS-fs (loop4): Unrecognized mount option "resgid=0x0000000000000000" or missing value
netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'.