bisecting fixing commit since 830a059cbba6832c11fefc0894c7ec7a27f75734 building syzkaller on 6a81331a1d4c744da9204d02ec88d558f7eea9c9 testing commit 830a059cbba6832c11fefc0894c7ec7a27f75734 with gcc (GCC) 8.4.1 20210217 kernel signature: 6294e7469c2e35b79c0b671f61a79d7ea10e3965d6d330fab2d1c22357cc340c all runs: crashed: WARNING in cfg80211_connect testing current HEAD 3c8c23092588a23bf1856a64f58c37f477a413be testing commit 3c8c23092588a23bf1856a64f58c37f477a413be with gcc (GCC) 8.4.1 20210217 kernel signature: 4d37a99c0f49b4bcc0b3cea11a2ff2f2386e28bb56f9273e8f6783b22e579835 all runs: OK # git bisect start 3c8c23092588a23bf1856a64f58c37f477a413be 830a059cbba6832c11fefc0894c7ec7a27f75734 Bisecting: 76 revisions left to test after this (roughly 6 steps) [f59a6ec295a5e7cc75feefbd7903243322de338f] driver core: Fix locking bug in deferred_probe_timeout_work_func() testing commit f59a6ec295a5e7cc75feefbd7903243322de338f with gcc (GCC) 8.4.1 20210217 kernel signature: e64e4543880997f34f2b5ab3129086bcc110f27cb40e7fd2d2af06c04b5c7853 all runs: OK # git bisect bad f59a6ec295a5e7cc75feefbd7903243322de338f Bisecting: 38 revisions left to test after this (roughly 5 steps) [b89b5b030c1ea2ce4811766faadec0ee49d793b2] net:tipc: Fix a double free in tipc_sk_mcast_rcv testing commit b89b5b030c1ea2ce4811766faadec0ee49d793b2 with gcc (GCC) 8.4.1 20210217 kernel signature: 24acd43acea76cb17f80f70cabda2711b77b1eba5d76fead10ec974b8e971596 all runs: crashed: WARNING in cfg80211_connect # git bisect good b89b5b030c1ea2ce4811766faadec0ee49d793b2 Bisecting: 19 revisions left to test after this (roughly 4 steps) [5983b9de012edaa1149c3114e56c82ec6e9dd957] net: ieee802154: nl-mac: fix check on panid testing commit 5983b9de012edaa1149c3114e56c82ec6e9dd957 with gcc (GCC) 8.4.1 20210217 kernel signature: 405b57f8e0452d1a76e34d357d4266f54aab9f82ff21a981fe75c9c5b0777472 all runs: OK # git bisect bad 5983b9de012edaa1149c3114e56c82ec6e9dd957 Bisecting: 9 revisions left to test after this (roughly 3 steps) [7d2426a41f8d8f4e9164a3d2e2b7081c5b825609] net/mlx5: Fix placement of log_max_flow_counter testing commit 7d2426a41f8d8f4e9164a3d2e2b7081c5b825609 with gcc (GCC) 8.4.1 20210217 kernel signature: 47ef03d2f042c6b1814a16bed31aba5d1bf697f51e21dd50809d31f10a97fd9f all runs: crashed: WARNING in cfg80211_connect # git bisect good 7d2426a41f8d8f4e9164a3d2e2b7081c5b825609 Bisecting: 4 revisions left to test after this (roughly 2 steps) [ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1] cfg80211: remove WARN_ON() in cfg80211_sme_connect testing commit ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1 with gcc (GCC) 8.4.1 20210217 kernel signature: b2d5683d4b245d7bc6df61fc5691a67aa6d08740fb6ca344a99d83ee944d2738 all runs: OK # git bisect bad ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1 Bisecting: 2 revisions left to test after this (roughly 1 step) [814b7cf4c6d3e492c6105eb4b7e97563bc61cb60] RDMA/cxgb4: check for ipv6 address properly while destroying listener testing commit 814b7cf4c6d3e492c6105eb4b7e97563bc61cb60 with gcc (GCC) 8.4.1 20210217 kernel signature: 47ef03d2f042c6b1814a16bed31aba5d1bf697f51e21dd50809d31f10a97fd9f all runs: crashed: WARNING in cfg80211_connect # git bisect good 814b7cf4c6d3e492c6105eb4b7e97563bc61cb60 Bisecting: 0 revisions left to test after this (roughly 1 step) [b376516dbdac3657b1d4cb9d33ae368280377de2] net: sched: bump refcount for new action in ACT replace mode testing commit b376516dbdac3657b1d4cb9d33ae368280377de2 with gcc (GCC) 8.4.1 20210217 kernel signature: c5001a68bda258aa85861cef5640ba2299f316f41aa045f83988dd187dbf7fb2 all runs: crashed: WARNING in cfg80211_connect # git bisect good b376516dbdac3657b1d4cb9d33ae368280377de2 ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1 is the first bad commit commit ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1 Author: Du Cheng Date: Thu Apr 8 00:27:56 2021 +0800 cfg80211: remove WARN_ON() in cfg80211_sme_connect commit 1b5ab825d9acc0f27d2f25c6252f3526832a9626 upstream. A WARN_ON(wdev->conn) would trigger in cfg80211_sme_connect(), if multiple send_msg(NL80211_CMD_CONNECT) system calls are made from the userland, which should be anticipated and handled by the wireless driver. Remove this WARN_ON() to prevent kernel panic if kernel is configured to "panic_on_warn". Bug reported by syzbot. Reported-by: syzbot+5f9392825de654244975@syzkaller.appspotmail.com Signed-off-by: Du Cheng Link: https://lore.kernel.org/r/20210407162756.6101-1-ducheng2@gmail.com Signed-off-by: Johannes Berg Signed-off-by: Greg Kroah-Hartman net/wireless/sme.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) culprit signature: b2d5683d4b245d7bc6df61fc5691a67aa6d08740fb6ca344a99d83ee944d2738 parent signature: c5001a68bda258aa85861cef5640ba2299f316f41aa045f83988dd187dbf7fb2 revisions tested: 9, total time: 2h18m38.494803976s (build: 1h16m38.735369179s, test: 1h0m51.684896934s) first good commit: ee1a5262eb01fc347de97b0d3e0bc0e6f83ad8e1 cfg80211: remove WARN_ON() in cfg80211_sme_connect recipients (to): ["ducheng2@gmail.com" "gregkh@linuxfoundation.org" "johannes.berg@intel.com"] recipients (cc): []