From: Eric Biggers <ebiggers@kernel.org>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jiwei Sun <jiwei.sun@windriver.com>,
linux-rtc@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+08116743f8ad6f9a6de7@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: [rtc] Re: BUG: workqueue lockup (4)
Date: Mon, 10 Jun 2019 16:49:59 -0700 [thread overview]
Message-ID: <20190610234959.GB220379@gmail.com> (raw)
In-Reply-To: <20181007193918.GC32272@piout.net>
On Sun, Oct 07, 2018 at 09:39:18PM +0200, Alexandre Belloni wrote:
> 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.
>
Is there any plan to actually fix this? Because this bug is still open, syzbot
isn't able to report "workqueue lockup" bugs elsewhere in the kernel.
- Eric
next prev parent reply other threads:[~2019-06-10 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 12:15 BUG: workqueue lockup (4) syzbot
2018-10-07 12:18 ` Dmitry Vyukov
2018-10-07 19:39 ` Alexandre Belloni
2019-06-10 23:49 ` Eric Biggers [this message]
2019-06-11 6:59 ` [rtc] " 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=20190610234959.GB220379@gmail.com \
--to=ebiggers@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=dvyukov@google.com \
--cc=jiwei.sun@windriver.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 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.