bisecting fixing commit since ddef1e8e3f6eb26034833b7255e3fa584d54a230 building syzkaller on 76630fc9477809305ab0fc257f92826e7671cb7e testing commit ddef1e8e3f6eb26034833b7255e3fa584d54a230 with gcc (GCC) 8.1.0 kernel signature: bbf074e256a10796510ee069432cb2f79fd8288f run #0: crashed: possible deadlock in flush_workqueue run #1: crashed: possible deadlock in flush_workqueue run #2: crashed: possible deadlock in flush_workqueue run #3: crashed: possible deadlock in refcount_dec_and_mutex_lock run #4: crashed: possible deadlock in flush_workqueue run #5: crashed: possible deadlock in refcount_dec_and_mutex_lock run #6: crashed: possible deadlock in refcount_dec_and_mutex_lock run #7: crashed: possible deadlock in refcount_dec_and_mutex_lock run #8: crashed: possible deadlock in refcount_dec_and_mutex_lock run #9: crashed: possible deadlock in refcount_dec_and_mutex_lock testing current HEAD bfb9e5c03076a446b1f4f6a523ddc8d723c907a6 testing commit bfb9e5c03076a446b1f4f6a523ddc8d723c907a6 with gcc (GCC) 8.1.0 kernel signature: 4af8c2955715373f52e0ebd0b07724a7bd02e934 all runs: OK # git bisect start bfb9e5c03076a446b1f4f6a523ddc8d723c907a6 ddef1e8e3f6eb26034833b7255e3fa584d54a230 Bisecting: 683 revisions left to test after this (roughly 10 steps) [4e846d399cde242861c0705a702d95a0e707d4fc] vhost/vsock: split packets to send using multiple buffers testing commit 4e846d399cde242861c0705a702d95a0e707d4fc with gcc (GCC) 8.1.0 kernel signature: da1d1bc69d5a5523e3ecea2bb696f7c8d986be33 all runs: OK # git bisect bad 4e846d399cde242861c0705a702d95a0e707d4fc Bisecting: 341 revisions left to test after this (roughly 9 steps) [bf95ccce798daaf0a0dbea2927d51894a45b9d7d] iio: adc: max9611: explicitly cast gain_selectors testing commit bf95ccce798daaf0a0dbea2927d51894a45b9d7d with gcc (GCC) 8.1.0 kernel signature: 3f0b2e5cb0855fb206ce1a7bcfdbd621311a227f all runs: OK # git bisect bad bf95ccce798daaf0a0dbea2927d51894a45b9d7d Bisecting: 170 revisions left to test after this (roughly 8 steps) [a49ecc872d61a90a7ab78513113ffd124b29576a] qede: fix NULL pointer deref in __qede_remove() testing commit a49ecc872d61a90a7ab78513113ffd124b29576a with gcc (GCC) 8.1.0 kernel signature: ef2cd77d15dd63121be5be923705f9ed957fba53 all runs: OK # git bisect bad a49ecc872d61a90a7ab78513113ffd124b29576a Bisecting: 85 revisions left to test after this (roughly 7 steps) [c87091ed19935f90b6cfefd8e984c41b47caed65] llc: fix sk_buff leak in llc_conn_service() testing commit c87091ed19935f90b6cfefd8e984c41b47caed65 with gcc (GCC) 8.1.0 kernel signature: bd3a084d334bb906d9e89d3ab70905b2c2c99861 run #0: basic kernel testing failed: failed to copy test binary to VM: failed to run ["scp" "-P" "22" "-F" "/dev/null" "-o" "UserKnownHostsFile=/dev/null" "-o" "BatchMode=yes" "-o" "IdentitiesOnly=yes" "-o" "StrictHostKeyChecking=no" "-o" "ConnectTimeout=10" "-i" "/syzkaller/jobs/linux/workdir/image/key" "/tmp/syz-executor473615217" "root@10.128.1.42:./syz-executor473615217"]: exit status 1 ssh: connect to host 10.128.1.42 port 22: Connection timed out lost connection run #1: OK run #2: OK run #3: OK run #4: OK run #5: OK run #6: OK run #7: OK run #8: OK run #9: OK # git bisect bad c87091ed19935f90b6cfefd8e984c41b47caed65 Bisecting: 42 revisions left to test after this (roughly 5 steps) [a59335e1f8a77ba42c4c3620996dd120fd2ab801] efi/x86: Do not clean dummy variable in kexec path testing commit a59335e1f8a77ba42c4c3620996dd120fd2ab801 with gcc (GCC) 8.1.0 kernel signature: 43615c3ce2516da84fa00b2f0e8d5b45131c9f48 run #0: crashed: possible deadlock in flush_workqueue run #1: crashed: possible deadlock in flush_workqueue run #2: crashed: possible deadlock in flush_workqueue run #3: crashed: possible deadlock in refcount_dec_and_mutex_lock run #4: crashed: possible deadlock in refcount_dec_and_mutex_lock run #5: crashed: possible deadlock in refcount_dec_and_mutex_lock run #6: crashed: possible deadlock in flush_workqueue run #7: crashed: possible deadlock in refcount_dec_and_mutex_lock run #8: crashed: possible deadlock in refcount_dec_and_mutex_lock run #9: crashed: possible deadlock in flush_workqueue # git bisect good a59335e1f8a77ba42c4c3620996dd120fd2ab801 Bisecting: 21 revisions left to test after this (roughly 5 steps) [93f4021f0dd62089db7c56a767f6a92cb9473dee] fuse: truncate pending writes on O_TRUNC testing commit 93f4021f0dd62089db7c56a767f6a92cb9473dee with gcc (GCC) 8.1.0 kernel signature: ad5ee1b6c82f66edb66a0c8cb325ae68c872b1c8 all runs: OK # git bisect bad 93f4021f0dd62089db7c56a767f6a92cb9473dee Bisecting: 10 revisions left to test after this (roughly 3 steps) [205cb89c17cb490ffbfe55c9e6ae1c6ee5366ea5] MIPS: fw: sni: Fix out of bounds init of o32 stack testing commit 205cb89c17cb490ffbfe55c9e6ae1c6ee5366ea5 with gcc (GCC) 8.1.0 kernel signature: 080b8e952fc96b453d4aca8da17d57d9ec86e5d6 run #0: crashed: possible deadlock in refcount_dec_and_mutex_lock run #1: crashed: possible deadlock in refcount_dec_and_mutex_lock run #2: crashed: possible deadlock in flush_workqueue run #3: crashed: possible deadlock in flush_workqueue run #4: crashed: possible deadlock in refcount_dec_and_mutex_lock run #5: crashed: possible deadlock in refcount_dec_and_mutex_lock run #6: crashed: possible deadlock in refcount_dec_and_mutex_lock run #7: crashed: possible deadlock in flush_workqueue run #8: crashed: possible deadlock in flush_workqueue run #9: crashed: possible deadlock in flush_workqueue # git bisect good 205cb89c17cb490ffbfe55c9e6ae1c6ee5366ea5 Bisecting: 5 revisions left to test after this (roughly 3 steps) [4df728651b8a99693c69962d8e5a5b9e5a3bbcc7] nbd: verify socket is supported during setup testing commit 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 with gcc (GCC) 8.1.0 kernel signature: 14c1a3833865bea017d24dce67b4f4a576f0fc10 all runs: OK # git bisect bad 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 Bisecting: 2 revisions left to test after this (roughly 1 step) [640fb32d61f32d1011bf9a96805e5a8d033abcea] NFSv4: Fix leak of clp->cl_acceptor string testing commit 640fb32d61f32d1011bf9a96805e5a8d033abcea with gcc (GCC) 8.1.0 kernel signature: 0809f1bff27421bd095e0a8e7aca0b2d5081beac run #0: crashed: possible deadlock in flush_workqueue run #1: crashed: possible deadlock in flush_workqueue run #2: crashed: possible deadlock in refcount_dec_and_mutex_lock run #3: crashed: possible deadlock in flush_workqueue run #4: crashed: possible deadlock in refcount_dec_and_mutex_lock run #5: crashed: possible deadlock in refcount_dec_and_mutex_lock run #6: crashed: possible deadlock in refcount_dec_and_mutex_lock run #7: crashed: possible deadlock in refcount_dec_and_mutex_lock run #8: crashed: possible deadlock in refcount_dec_and_mutex_lock run #9: crashed: possible deadlock in flush_workqueue # git bisect good 640fb32d61f32d1011bf9a96805e5a8d033abcea Bisecting: 0 revisions left to test after this (roughly 1 step) [2a7ad49ad210e80780964807f241eeb3bdc23f1f] tracing: Initialize iter->seq after zeroing in tracing_read_pipe() testing commit 2a7ad49ad210e80780964807f241eeb3bdc23f1f with gcc (GCC) 8.1.0 kernel signature: 90c67870259c4153403b5c52ea7d90e3b4752735 run #0: crashed: possible deadlock in flush_workqueue run #1: crashed: possible deadlock in refcount_dec_and_mutex_lock run #2: crashed: possible deadlock in flush_workqueue run #3: crashed: possible deadlock in refcount_dec_and_mutex_lock run #4: crashed: possible deadlock in refcount_dec_and_mutex_lock run #5: crashed: possible deadlock in flush_workqueue run #6: crashed: possible deadlock in refcount_dec_and_mutex_lock run #7: crashed: possible deadlock in refcount_dec_and_mutex_lock run #8: crashed: possible deadlock in refcount_dec_and_mutex_lock run #9: crashed: possible deadlock in flush_workqueue # git bisect good 2a7ad49ad210e80780964807f241eeb3bdc23f1f 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 is the first bad commit commit 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 Author: Mike Christie Date: Thu Oct 17 16:27:34 2019 -0500 nbd: verify socket is supported during setup [ Upstream commit cf1b2326b734896734c6e167e41766f9cee7686a ] nbd requires socket families to support the shutdown method so the nbd recv workqueue can be woken up from its sock_recvmsg call. If the socket does not support the callout we will leave recv works running or get hangs later when the device or module is removed. This adds a check during socket connection/reconnection to make sure the socket being passed in supports the needed callout. Reported-by: syzbot+24c12fa8d218ed26011a@syzkaller.appspotmail.com Fixes: e9e006f5fcf2 ("nbd: fix max number of supported devs") Tested-by: Richard W.M. Jones Signed-off-by: Mike Christie Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin drivers/block/nbd.c | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) culprit signature: 14c1a3833865bea017d24dce67b4f4a576f0fc10 parent signature: 90c67870259c4153403b5c52ea7d90e3b4752735 revisions tested: 12, total time: 3h5m32.396309794s (build: 1h36m34.968835047s, test: 1h27m43.523644085s) first good commit: 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 nbd: verify socket is supported during setup cc: ["axboe@kernel.dk" "mchristi@redhat.com" "rjones@redhat.com" "sashal@kernel.org"]