From: Oleg Nesterov <oleg@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: syzbot <syzbot+cef555184e66963dabc2@syzkaller.appspotmail.com>,
boqun.feng@gmail.com, brauner@kernel.org,
cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, lizefan.x@bytedance.com,
longman@redhat.com, michael.christie@oracle.com,
mingo@redhat.com, mst@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, wander@redhat.com,
will@kernel.org
Subject: Re: [syzbot] [cgroups?] possible deadlock in cgroup_free
Date: Sun, 19 Nov 2023 16:30:28 +0100 [thread overview]
Message-ID: <20231119153028.GB29401@redhat.com> (raw)
In-Reply-To: <ZVolxA8RHsY11CnE@slm.duckdns.org>
On 11/19, Tejun Heo wrote:
>
> On Thu, Nov 16, 2023 at 05:25:05PM -0800, syzbot wrote:
> > 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
>
> Looks like the tasklist_lock conversion in ptrace_attach() forgot _irq.
> Peter, Oleg?
Yes, please see
Re: [syzbot] [kernel?] inconsistent lock state in ptrace_attach
https://lore.kernel.org/all/20231117094531.GN8262@noisy.programming.kicks-ass.net/
Oleg.
next prev parent reply other threads:[~2023-11-19 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:08 [syzbot] [cgroups?] possible deadlock in cgroup_free syzbot
2023-11-16 14:16 ` syzbot
2023-11-17 1:25 ` syzbot
2023-11-19 15:12 ` Tejun Heo
2023-11-19 15:30 ` Oleg Nesterov [this message]
2023-11-17 10:58 ` [syzbot] Test syzbot
[not found] <CAJjsb4rUe+sOAY_rbUZuyHFKQzmo4TGvOhZsHF_T+8zjw6CBrA@mail.gmail.com>
2023-11-17 11:53 ` [syzbot] [cgroups?] possible deadlock in cgroup_free 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=20231119153028.GB29401@redhat.com \
--to=oleg@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=michael.christie@oracle.com \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+cef555184e66963dabc2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox