From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+a9fb1457d720a55d6dc5@syzkaller.appspotmail.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
allison@lohutok.net, areber@redhat.com,
aubrey.li@linux.intel.com, Andrei Vagin <avagin@gmail.com>,
Bruce Fields <bfields@fieldses.org>,
Christian Brauner <christian@brauner.io>,
cyphar@cyphar.com, "Eric W. Biederman" <ebiederm@xmission.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
guro@fb.com, Jeff Layton <jlayton@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Kees Cook <keescook@chromium.org>,
linmiaohe@huawei.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>, Ingo Molnar <mingo@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
sargun@sargun.me,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>,
Al Viro <viro@zeniv.linux.org.uk>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: possible deadlock in send_sigio
Date: Thu, 11 Jun 2020 12:09:59 -0400 [thread overview]
Message-ID: <b405aca6-a3b2-cf11-a482-2b4af1e548bd@redhat.com> (raw)
In-Reply-To: <20200611142214.GI2531@hirez.programming.kicks-ass.net>
On 6/11/20 10:22 AM, Peter Zijlstra wrote:
> On Thu, Jun 11, 2020 at 09:51:29AM -0400, Waiman Long wrote:
>
>> There was an old lockdep patch that I think may address the issue, but was
>> not merged at the time. I will need to dig it out and see if it can be
>> adapted to work in the current kernel. It may take some time.
> Boqun was working on that; I can't remember what happened, but ISTR it
> was shaping up nice.
>
Yes, I am talking about Boqun's patch. However, I think he had moved to
another company and so may not be able to actively work on that again.
Cheers,
Longman
next prev parent reply other threads:[~2020-06-11 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 5:55 possible deadlock in send_sigio syzbot
2020-06-11 2:32 ` Waiman Long
2020-06-11 7:43 ` Dmitry Vyukov
2020-06-11 13:51 ` Waiman Long
2020-06-11 14:22 ` Peter Zijlstra
2020-06-11 16:09 ` Waiman Long [this message]
2020-06-11 23:55 ` Boqun Feng
2020-06-12 1:55 ` Waiman Long
2020-06-12 7:01 ` Boqun Feng
2020-06-15 16:37 ` Waiman Long
2020-06-15 16:49 ` Matthew Wilcox
2020-06-15 17:13 ` Waiman Long
2020-06-15 20:40 ` Matthew Wilcox
2020-06-16 0:13 ` Boqun Feng
2020-06-16 0:31 ` Waiman Long
2020-06-11 16:07 ` Eric W. Biederman
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=b405aca6-a3b2-cf11-a482-2b4af1e548bd@redhat.com \
--to=longman@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=allison@lohutok.net \
--cc=areber@redhat.com \
--cc=aubrey.li@linux.intel.com \
--cc=avagin@gmail.com \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=christian@brauner.io \
--cc=cyphar@cyphar.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=jlayton@kernel.org \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sargun@sargun.me \
--cc=syzbot+a9fb1457d720a55d6dc5@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).