bisecting fixing commit since ddef1e8e3f6eb26034833b7255e3fa584d54a230 building syzkaller on d603afc9e4ab932977582f4be7f9ce2375411236 testing commit ddef1e8e3f6eb26034833b7255e3fa584d54a230 with gcc (GCC) 8.1.0 kernel signature: 9ab7c41d01dfb2c40235f6ed016eb45ee57f91d4fbdb7f5a24cf8628d9d55b82 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 refcount_dec_and_mutex_lock run #3: crashed: possible deadlock in flush_workqueue run #4: crashed: possible deadlock in flush_workqueue 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 refcount_dec_and_mutex_lock testing current HEAD 8bac50406cca10a219aa899243d49c57ddaf7c5b testing commit 8bac50406cca10a219aa899243d49c57ddaf7c5b with gcc (GCC) 8.1.0 kernel signature: 562ea4ea620d251818a24056d65274dbd14e02e6f3b49284f7061bf0de7d64c2 all runs: OK # git bisect start 8bac50406cca10a219aa899243d49c57ddaf7c5b ddef1e8e3f6eb26034833b7255e3fa584d54a230 Bisecting: 986 revisions left to test after this (roughly 10 steps) [94848ffd66c2ddcb725a296b71b5f8dbe2cbeaa2] IB/rxe: Make counters thread safe testing commit 94848ffd66c2ddcb725a296b71b5f8dbe2cbeaa2 with gcc (GCC) 8.1.0 kernel signature: 3c9e90df5f02504014bda50b47d97d4f6e44ab3f5ed6955bad06f264827bebfb all runs: OK # git bisect bad 94848ffd66c2ddcb725a296b71b5f8dbe2cbeaa2 Bisecting: 492 revisions left to test after this (roughly 9 steps) [16afeb2513f8540d7e40aabc7d5bd3413f8a96de] media: pci: ivtv: Fix a sleep-in-atomic-context bug in ivtv_yuv_init() testing commit 16afeb2513f8540d7e40aabc7d5bd3413f8a96de with gcc (GCC) 8.1.0 kernel signature: 0436f26f7e4b8380f1fff838c504f2de630fcdaf4be5103b2ed7fdbd3e0f0eae all runs: OK # git bisect bad 16afeb2513f8540d7e40aabc7d5bd3413f8a96de Bisecting: 246 revisions left to test after this (roughly 8 steps) [938449fdd37743e72eb386272360543468a2a101] perf/x86/amd/ibs: Fix reading of the IBS OpData register and thus precise RIP validity testing commit 938449fdd37743e72eb386272360543468a2a101 with gcc (GCC) 8.1.0 kernel signature: b70f0fd3c36c8c971e7ee89737e5ae6864ff0bf8e82947dfa15f710c26e9ee8b all runs: OK # git bisect bad 938449fdd37743e72eb386272360543468a2a101 Bisecting: 122 revisions left to test after this (roughly 7 steps) [2d8cd1c2e556e39ae6eb9d5e629c5c0f1801cf06] net: annotate lockless accesses to sk->sk_napi_id testing commit 2d8cd1c2e556e39ae6eb9d5e629c5c0f1801cf06 with gcc (GCC) 8.1.0 kernel signature: b7ae4e7657a1f1874c078a9249082d0aba3acdf9317d55172fd8d3bb20658d54 all runs: OK # git bisect bad 2d8cd1c2e556e39ae6eb9d5e629c5c0f1801cf06 Bisecting: 61 revisions left to test after this (roughly 6 steps) [ce1dee3c1a88a534f561310f16e2eed3e686f28a] ath6kl: fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe() testing commit ce1dee3c1a88a534f561310f16e2eed3e686f28a with gcc (GCC) 8.1.0 kernel signature: 69ebb74323c677eae1e5f5042ad6c44d86902017d5ad986646a41776a3502395 all runs: OK # git bisect bad ce1dee3c1a88a534f561310f16e2eed3e686f28a Bisecting: 30 revisions left to test after this (roughly 5 steps) [8c2a577c879c43085c65d7130b581bb53376b3ea] staging: rtl8188eu: fix null dereference when kzalloc fails testing commit 8c2a577c879c43085c65d7130b581bb53376b3ea with gcc (GCC) 8.1.0 kernel signature: 4c4fd12b733c6c9cb4e218155651727580d3cdc79791ce2778622b5342a32c8d 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 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 flush_workqueue run #7: crashed: possible deadlock in flush_workqueue run #8: crashed: possible deadlock in refcount_dec_and_mutex_lock run #9: crashed: possible deadlock in refcount_dec_and_mutex_lock # git bisect good 8c2a577c879c43085c65d7130b581bb53376b3ea Bisecting: 15 revisions left to test after this (roughly 4 steps) [7864c58e02ad9c8ee3c1a2712a6df9a26093a3b5] ocfs2: clear zero in unaligned direct IO testing commit 7864c58e02ad9c8ee3c1a2712a6df9a26093a3b5 with gcc (GCC) 8.1.0 kernel signature: 62db70b3467e789c6e21b9f76edbbaa27e06000c37920ea9060f437cb28f3c73 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 flush_workqueue 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 flush_workqueue run #9: crashed: possible deadlock in flush_workqueue # git bisect good 7864c58e02ad9c8ee3c1a2712a6df9a26093a3b5 Bisecting: 7 revisions left to test after this (roughly 3 steps) [ff9edf3f778cb853a18dd00e1c1820df8a4e183e] nbd: fix possible sysfs duplicate warning testing commit ff9edf3f778cb853a18dd00e1c1820df8a4e183e with gcc (GCC) 8.1.0 kernel signature: c1afd72d987b9562958a0ea8d38fa912cda765707be273e10c3e0a531cf71af3 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 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 # git bisect good ff9edf3f778cb853a18dd00e1c1820df8a4e183e Bisecting: 3 revisions left to test after this (roughly 2 steps) [4df728651b8a99693c69962d8e5a5b9e5a3bbcc7] nbd: verify socket is supported during setup testing commit 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 with gcc (GCC) 8.1.0 kernel signature: 849478e3b29879a43b0313c565ce8e6c648af3f8c09a34058922c86eb92be6bd all runs: OK # git bisect bad 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 Bisecting: 1 revision left to test after this (roughly 1 step) [fbfd8dadf521784fd2fbb1cfc61e318979593c41] s390/uaccess: avoid (false positive) compiler warnings testing commit fbfd8dadf521784fd2fbb1cfc61e318979593c41 with gcc (GCC) 8.1.0 kernel signature: 98e564330c8ee329ad66128ca58abfafb87581229937f1a092f1fe78f082e259 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 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 refcount_dec_and_mutex_lock # git bisect good fbfd8dadf521784fd2fbb1cfc61e318979593c41 Bisecting: 0 revisions left to test after this (roughly 0 steps) [2a7ad49ad210e80780964807f241eeb3bdc23f1f] tracing: Initialize iter->seq after zeroing in tracing_read_pipe() testing commit 2a7ad49ad210e80780964807f241eeb3bdc23f1f with gcc (GCC) 8.1.0 kernel signature: d0085c14d5a1a3462e5c73a7a42570b8a7a0d3de95bb1d8461f0ffe491bd9a9d 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 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 flush_workqueue run #8: crashed: possible deadlock in flush_workqueue run #9: crashed: possible deadlock in refcount_dec_and_mutex_lock # 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: 849478e3b29879a43b0313c565ce8e6c648af3f8c09a34058922c86eb92be6bd parent signature: d0085c14d5a1a3462e5c73a7a42570b8a7a0d3de95bb1d8461f0ffe491bd9a9d revisions tested: 13, total time: 3h46m17.044334211s (build: 1h50m1.570512585s, test: 1h54m35.837092821s) first good commit: 4df728651b8a99693c69962d8e5a5b9e5a3bbcc7 nbd: verify socket is supported during setup cc: ["axboe@kernel.dk" "mchristi@redhat.com" "rjones@redhat.com" "sashal@kernel.org"]