From: syzbot <syzbot+cbb25bb9b4d29a773985@syzkaller.appspotmail.com>
To: boqun.feng@gmail.com, brauner@kernel.org,
linux-kernel@vger.kernel.org, longman@redhat.com,
michael.christie@oracle.com, mingo@redhat.com, mst@redhat.com,
oleg@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
wander@redhat.com, will@kernel.org
Subject: Re: [syzbot] [kernel?] inconsistent lock state in ptrace_attach
Date: Fri, 17 Nov 2023 00:49:04 -0800 [thread overview]
Message-ID: <00000000000064b787060a55354e@google.com> (raw)
In-Reply-To: <000000000000a25ea7060a430d3c@google.com>
syzbot has bisected this issue to:
commit 2d25a889601d2fbc87ec79b30ea315820f874b78
Author: Peter Zijlstra <peterz@infradead.org>
Date: Sun Sep 17 11:24:21 2023 +0000
ptrace: Convert ptrace_attach() to use lock guards
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132b7d84e80000
start commit: f31817cbcf48 Add linux-next specific files for 20231116
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10ab7d84e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=172b7d84e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f59345f1d0a928c
dashboard link: https://syzkaller.appspot.com/bug?extid=cbb25bb9b4d29a773985
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1014d797680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b1ec67680000
Reported-by: syzbot+cbb25bb9b4d29a773985@syzkaller.appspotmail.com
Fixes: 2d25a889601d ("ptrace: Convert ptrace_attach() to use lock guards")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-17 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in ptrace_attach syzbot
2023-11-16 20:00 ` syzbot
2023-11-17 8:49 ` syzbot [this message]
2023-11-17 9:27 ` Peter Zijlstra
2023-11-17 9:38 ` Oleg Nesterov
2023-11-17 9:45 ` Peter Zijlstra
2023-11-17 12:32 ` Oleg Nesterov
2023-11-17 13:51 ` [syzbot] Test syzbot
[not found] <CAJjsb4rmXhLyOFpNwQy1kh480Q7p=gvTY5HnhF-b=Sf=VijYKA@mail.gmail.com>
2023-11-17 14:12 ` [syzbot] [kernel?] inconsistent lock state in ptrace_attach syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000064b787060a55354e@google.com \
--to=syzbot+cbb25bb9b4d29a773985@syzkaller.appspotmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=michael.christie@oracle.com \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=wander@redhat.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.