From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+08116743f8ad6f9a6de7@syzkaller.appspotmail.com>,
a.zummo@towertech.it, linux-rtc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: BUG: workqueue lockup (4)
Date: Sun, 7 Oct 2018 21:39:18 +0200 [thread overview]
Message-ID: <20181007193918.GC32272@piout.net> (raw)
In-Reply-To: <CACT4Y+ZAoLro6LHhaA2EuWF1nAWAA=NAVtpMammhspL4V2aMgw@mail.gmail.com>
Hi,
On 07/10/2018 14:18:31+0200, Dmitry Vyukov wrote:
> On Sun, Oct 7, 2018 at 2:15 PM, syzbot
> <syzbot+08116743f8ad6f9a6de7@syzkaller.appspotmail.com> wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: c1d84a1b42ef Merge git://git.kernel.org/pub/scm/linux/kern..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14c5f491400000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
> > dashboard link: https://syzkaller.appspot.com/bug?extid=08116743f8ad6f9a6de7
> > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14514a6e400000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1025ebb9400000
>
> The reproducer seems to be all about rtc. So +rtc maintainers.
>
It seems to be that bug:
http://patchwork.ozlabs.org/patch/898552/
I'm pretty sure the fix is not correct though and didn't have the time
to work on a proper fix.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-07 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000005764090577a27486@google.com>
2018-10-07 12:18 ` BUG: workqueue lockup (4) Dmitry Vyukov
2018-10-07 19:39 ` Alexandre Belloni [this message]
2019-06-10 23:49 ` [rtc] " Eric Biggers
2019-06-11 6:59 ` Alexandre Belloni
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=20181007193918.GC32272@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=syzbot+08116743f8ad6f9a6de7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).