From: Peter Zijlstra <peterz@infradead.org>
To: syzbot <syzbot+6b6a46cc150b19f54ad6@syzkaller.appspotmail.com>
Cc: bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: WARNING: lock held when returning to user space in membarrier_private_expedited
Date: Tue, 1 Oct 2019 10:45:40 +0200 [thread overview]
Message-ID: <20191001084540.GO4519@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <000000000000ceadfd0593d4dd55@google.com>
On Tue, Oct 01, 2019 at 01:09:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: afb37288 Add linux-next specific files for 20191001
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17619635600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=659cb5bf73e72c6c
> dashboard link: https://syzkaller.appspot.com/bug?extid=6b6a46cc150b19f54ad6
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176faa13600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b825cd600000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+6b6a46cc150b19f54ad6@syzkaller.appspotmail.com
>
> ================================================
> WARNING: lock held when returning to user space!
> 5.4.0-rc1-next-20191001 #0 Not tainted
> ------------------------------------------------
> syz-executor589/9088 is leaving the kernel with locks still held!
> 1 lock held by syz-executor589/9088:
> #0: ffffffff88faadc0 (rcu_read_lock){....}, at:
> membarrier_private_expedited+0x180/0x590 kernel/sched/membarrier.c:150
https://lkml.kernel.org/r/20191001071921.GJ4519@hirez.programming.kicks-ass.net
prev parent reply other threads:[~2019-10-01 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 8:09 WARNING: lock held when returning to user space in membarrier_private_expedited syzbot
2019-10-01 8:45 ` Peter Zijlstra [this message]
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=20191001084540.GO4519@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+6b6a46cc150b19f54ad6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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