From: Eric Biggers <ebiggers@kernel.org>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-rtc@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 1 open syzbot bug in rtc subsystem
Date: Tue, 30 Jul 2019 19:33:41 -0700 [thread overview]
Message-ID: <20190731023341.GD687@sol.localdomain> (raw)
In-Reply-To: <20190724025008.GL643@sol.localdomain>
On Mon, Jul 29, 2019 at 03:47:45PM +0800, Hillf Danton wrote:
>
> On Tue, 23 Jul 2019 19:50:08 -0700
> >
> > [This email was generated by a script. Let me know if you have any suggestions
> > to make it better, or if you want it re-generated with the latest status.]
> >
> > Of the currently open syzbot reports against the upstream kernel, I've manually
> > marked 1 of them as possibly being a bug in the rtc subsystem.
> >
> > If you believe this bug is no longer valid, please close the syzbot report by
> > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the
> > original thread, as explained at https://goo.gl/tpsmEJ#status
> >
> > If you believe I misattributed this bug to the rtc subsystem, please let me
> > know, and if possible forward the report to the correct people or mailing list.
> >
> > Here is the bug:
> >
> > --------------------------------------------------------------------------------
> > Title: BUG: workqueue lockup (4)
> > Last occurred: 40 days ago
> > Reported: 289 days ago
> > Branches: Mainline and others
> > Dashboard link: https://syzkaller.appspot.com/bug?id=0041bf1423916e9ae458b08b760e269a33c14960
> > Original thread: https://lkml.kernel.org/lkml/0000000000005764090577a27486@google.com/T/#u
> >
> Better if %s=lkml.kernel.org=lore.kernel.org=
>
Out of curiosity, is there a reason for this? They both go to the same place,
but the reason I used lkml.kernel.org is that some high-profile kernel
developers (e.g. Andrew Morton) are using it in the "Link: " tag in commits.
So it seems like lkml.kernel.org is maybe "right" one that is intended to
always keep working in the future?
But then I see Greg KH is using lore.kernel.org, so maybe it doesn't matter?
Maybe lore.kernel.org is better because people won't confuse it with lkml.org
and refuse to go to it :-)
- Eric
next prev parent reply other threads:[~2019-07-31 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 2:50 Reminder: 1 open syzbot bug in rtc subsystem Eric Biggers
2019-07-28 13:23 ` Pavel Machek
2019-07-31 2:27 ` Eric Biggers
2019-08-02 10:24 ` Pavel Machek
2019-07-31 2:33 ` Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-02 5:10 Eric Biggers
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=20190731023341.GD687@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--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).