bisecting fixing commit since a42a7bb6f5362c77f38cdc5e2d05e9fe0c2ade2c building syzkaller on 749688d22abef3f3cb9a0480e15c19a3f2ed8e13 testing commit a42a7bb6f5362c77f38cdc5e2d05e9fe0c2ade2c with gcc (GCC) 8.1.0 kernel signature: 77b705f2ae737123b7c3528222ca0008cafa177aea359c19c22a602a4160e4f8 run #0: crashed: possible deadlock in seq_read run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: OK testing current HEAD 690e2aba7beb1ef06352803bea41a68a3c695015 testing commit 690e2aba7beb1ef06352803bea41a68a3c695015 with gcc (GCC) 8.1.0 kernel signature: a7abc5b356155af2b526610f7f5df279c153ba492c8ef9deb3e554309f1c99bd all runs: OK # git bisect start 690e2aba7beb1ef06352803bea41a68a3c695015 a42a7bb6f5362c77f38cdc5e2d05e9fe0c2ade2c Bisecting: 6369 revisions left to test after this (roughly 13 steps) [f365ab31efacb70bed1e821f7435626e0b2528a6] Merge tag 'drm-next-2020-04-01' of git://anongit.freedesktop.org/drm/drm testing commit f365ab31efacb70bed1e821f7435626e0b2528a6 with gcc (GCC) 8.1.0 kernel signature: eb3833d277ab2a4c1638a409f5b4beea0e616239470d500b43924814c780ce18 run #0: crashed: possible deadlock in lock_trace run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: OK # git bisect good f365ab31efacb70bed1e821f7435626e0b2528a6 Bisecting: 3175 revisions left to test after this (roughly 12 steps) [854e80bcfdafb8d99d308e21798cd0116338783d] Merge tag 'arm-dt-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc testing commit 854e80bcfdafb8d99d308e21798cd0116338783d with gcc (GCC) 8.1.0 kernel signature: debd5198fe1086c0d31286070ebb95b8079d28511e04602ae9140464509b5e50 all runs: OK # git bisect bad 854e80bcfdafb8d99d308e21798cd0116338783d Bisecting: 1591 revisions left to test after this (roughly 11 steps) [e964f1e04a1ce562f0d748b29326244d3cb35ba4] Merge tag 'dmaengine-5.7-rc1' of git://git.infradead.org/users/vkoul/slave-dma testing commit e964f1e04a1ce562f0d748b29326244d3cb35ba4 with gcc (GCC) 8.1.0 kernel signature: d5515ff3934eeeb2d5f4d9b21431d0325c028c2373a9fbce3f8a2e990272e5c6 all runs: OK # git bisect bad e964f1e04a1ce562f0d748b29326244d3cb35ba4 Bisecting: 693 revisions left to test after this (roughly 10 steps) [8c1b724ddb218f221612d4c649bc9c7819d8d7a6] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm testing commit 8c1b724ddb218f221612d4c649bc9c7819d8d7a6 with gcc (GCC) 8.1.0 kernel signature: ce64f08efc9e05572555dacd598080c11d5c2b0b74a645f3f374b1115ba058cb all runs: OK # git bisect bad 8c1b724ddb218f221612d4c649bc9c7819d8d7a6 Bisecting: 450 revisions left to test after this (roughly 9 steps) [7be97138e7276c71cc9ad1752dcb502d28f4400d] Merge tag 'xfs-5.7-merge-8' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux testing commit 7be97138e7276c71cc9ad1752dcb502d28f4400d with gcc (GCC) 8.1.0 kernel signature: caf32543d76b392d41d84f76126779e3f34ffcd44d99b3522e4d22af72b2cbad all runs: OK # git bisect bad 7be97138e7276c71cc9ad1752dcb502d28f4400d Bisecting: 212 revisions left to test after this (roughly 8 steps) [919dce24701f7b34681a6a1d3ef95c9f6c4fb1cc] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma testing commit 919dce24701f7b34681a6a1d3ef95c9f6c4fb1cc with gcc (GCC) 8.1.0 kernel signature: 138aa7b2477b1f0f5943f77aa2bb3a401ae67d6848340d84ba4b0bb4b297c143 all runs: crashed: possible deadlock in lock_trace # git bisect good 919dce24701f7b34681a6a1d3ef95c9f6c4fb1cc Bisecting: 106 revisions left to test after this (roughly 7 steps) [d59f44d3e723c4f7143d910dfa333f2bdb587bbc] xfs: directory bestfree check should release buffers testing commit d59f44d3e723c4f7143d910dfa333f2bdb587bbc with gcc (GCC) 8.1.0 kernel signature: 2b892cdf986af46f0ca914a10467bd67f467deee6a9648de033bda69923ef9fd run #0: crashed: possible deadlock in seq_read run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: OK # git bisect good d59f44d3e723c4f7143d910dfa333f2bdb587bbc Bisecting: 53 revisions left to test after this (roughly 6 steps) [7ef482fa65513b18eed05a5c5f00413aad137810] helper for mount rootwards traversal testing commit 7ef482fa65513b18eed05a5c5f00413aad137810 with gcc (GCC) 8.1.0 kernel signature: 9e09d9e551df81f396a89b0870a97bb05401800f14fc264f5d6df08f49f41b5e run #0: crashed: possible deadlock in lock_trace run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: OK run #9: OK # git bisect good 7ef482fa65513b18eed05a5c5f00413aad137810 Bisecting: 26 revisions left to test after this (roughly 5 steps) [4b871ce26ab2c758ea90b8dd659e4267aae9e943] Merged 'Infrastructure to allow fixing exec deadlocks' from Bernd Edlinger testing commit 4b871ce26ab2c758ea90b8dd659e4267aae9e943 with gcc (GCC) 8.1.0 kernel signature: 201b842f395bd8319346f05f897b31d475c0df5c765dce05e6c28857c189ed4c all runs: OK # git bisect bad 4b871ce26ab2c758ea90b8dd659e4267aae9e943 Bisecting: 13 revisions left to test after this (roughly 4 steps) [2ca7be7d55ad84fb0f7c2a23fb700a28fd76b19a] exec: Only compute current once in flush_old_exec testing commit 2ca7be7d55ad84fb0f7c2a23fb700a28fd76b19a with gcc (GCC) 8.1.0 kernel signature: 251ec8daceb06e2e09be54c664ef2e6fc1f8c26ddabb1bd10306dcd78199681c run #0: crashed: possible deadlock in lock_trace run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: OK # git bisect good 2ca7be7d55ad84fb0f7c2a23fb700a28fd76b19a Bisecting: 6 revisions left to test after this (roughly 3 steps) [8d09db80ef404d8e2e143677e0716cfcd544e29b] mm: docs: Fix a comment in process_vm_rw_core testing commit 8d09db80ef404d8e2e143677e0716cfcd544e29b with gcc (GCC) 8.1.0 kernel signature: 15fc08dd0b236a5df78fc52680fb7a0397df8d08e108ce164220fe84a02b6d30 run #0: crashed: possible deadlock in seq_read run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: boot failed: can't ssh into the instance # git bisect good 8d09db80ef404d8e2e143677e0716cfcd544e29b Bisecting: 3 revisions left to test after this (roughly 2 steps) [2db9dbf71bf98d02a0bf33e798e5bfd2a9944696] proc: Use new infrastructure to fix deadlocks in execve testing commit 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 with gcc (GCC) 8.1.0 kernel signature: 729b21f4e635effb5489e5b8a569f5cd0b18ed4b61175f3e5eff2285b413474f all runs: OK # git bisect bad 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 Bisecting: 0 revisions left to test after this (roughly 1 step) [454e3126cb842388e22df6b3ac3da44062c00765] kernel/kcmp.c: Use new infrastructure to fix deadlocks in execve testing commit 454e3126cb842388e22df6b3ac3da44062c00765 with gcc (GCC) 8.1.0 kernel signature: 0ff052f24606fd1b8fb90cb0fb17c2a328112dfa7eefd61560607306db55261f run #0: crashed: possible deadlock in lock_trace run #1: crashed: possible deadlock in lock_trace run #2: crashed: possible deadlock in lock_trace run #3: crashed: possible deadlock in lock_trace run #4: crashed: possible deadlock in lock_trace run #5: crashed: possible deadlock in lock_trace run #6: crashed: possible deadlock in lock_trace run #7: crashed: possible deadlock in lock_trace run #8: crashed: possible deadlock in lock_trace run #9: OK # git bisect good 454e3126cb842388e22df6b3ac3da44062c00765 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 is the first bad commit commit 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 Author: Bernd Edlinger Date: Fri Mar 20 21:27:24 2020 +0100 proc: Use new infrastructure to fix deadlocks in execve This changes lock_trace to use the new exec_update_mutex instead of cred_guard_mutex. This fixes possible deadlocks when the trace is accessing /proc/$pid/stack for instance. This should be safe, as the credentials are only used for reading, and task->mm is updated on execve under the new exec_update_mutex. Signed-off-by: Bernd Edlinger Signed-off-by: Eric W. Biederman fs/proc/base.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) culprit signature: 729b21f4e635effb5489e5b8a569f5cd0b18ed4b61175f3e5eff2285b413474f parent signature: 0ff052f24606fd1b8fb90cb0fb17c2a328112dfa7eefd61560607306db55261f revisions tested: 15, total time: 4h3m1.896381152s (build: 1h31m31.243675452s, test: 2h29m49.448622922s) first good commit: 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 proc: Use new infrastructure to fix deadlocks in execve cc: ["adobriyan@gmail.com" "akpm@linux-foundation.org" "avagin@gmail.com" "bernd.edlinger@hotmail.de" "ebiederm@xmission.com" "linux-fsdevel@vger.kernel.org" "linux-kernel@vger.kernel.org"]