linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list
Date: Wed, 7 Apr 2021 13:21:28 +0200	[thread overview]
Message-ID: <3df9566e-bb08-f1e2-7afb-a14a28d2d64f@leemhuis.info> (raw)
In-Reply-To: <YG2CztxS4jTia8wM@kroah.com>


On 07.04.21 12:00, Greg KH wrote:
> On Wed, Apr 07, 2021 at 11:21:56AM +0200, Thorsten Leemhuis wrote:
>> Make people CC the recently created mailing list dedicated to Linux
>> kernel regressions when reporting one. Some paragraphs had to be
>> reshuffled and slightly rewritten during the process, as the text
>> otherwise would have gotten unnecessarily hard to follow.
>>
>> The new text also makes reporters include a line useful for automatic
>> regression tracking solution which does not exist yet, but is planned.
>> The term "#regzb" (short for regression bot) is inspired by the "#syz"
>> which can be used to communicate with syszbot (see
>> https://github.com/google/syzkaller/blob/master/docs/syzbot.md).
> 
> While I understand the wish to automate things like this, the #syz
> marking will actually cause something to go off and do some work, and is
> only relevant for a very small number of developers, all of whom know to
> look up the instructions before doing so.  But the #regzb marking will
> be requested to be added by random users who never have submitted a
> problem report before, OR from long-time kernel developers who are lucky
> to ever remember to read the documentation as they "know" how to do
> this.
> 
> So this increased workload by people on the two ends of experience is
> going to be rough, I predict a very low rate of adoption :(

Yup, I'm aware of that. And also well aware that I will need to keep an
eye on things and jump in and reply with mails to add such tags every
time they are missing.
But I think that direction it the best shot, as tying putting all the
burden on one person (me) is likely to fail, as our history with
regression tracking showed. And I think such tags with some bot in the
background
(as outlined roughly in
https://linux-regtracking.leemhuis.info/post/hello-world/ ) have at
least the best chance, as things are not out-of-band like tracking them
in bugzilla would be – or do you think that would be a better approach
together with its email-interface?

> What is the tag going to be good for?  The reports will need to be
> handled by a person anyway and classified and tracked out-of-band from
> the list somehow.  Will a tag do all that much here?

I think is has, as then a good regression report will make the
still-to-be-written regression-bot create and entry that links to the
report and send a reply with a unique ID; then that ID needs to end up
in the commit that fixes the regression later (similar to how the IDs
for issues found by syzbot are mentioned there, which afaics works quite
well for people) and the regression-bot can close the entry automatically.

At least in this ideal scenario the regression tracker (me) wouldn't
need to do a single thing.

Obviously that ideal scenario will be rare, especially in the beginning.
But with some hand-holding from my side (by mailing tags) I hope it will
work at least sometimes (and over time more often).

But I'm open for other approaches, as I didn't start to work on the bot
yet(¹), so it's easy to go into a different direction if someone comes
up with one that looks more promising.

Ciao, Thorsten

(¹) still unsure if I should take Go code from syzbot as a base or
better go with python, as that's what the kernel.org admins iirc prefer
(or am I wrong there? I wanted to ask Konstantin about this soon anyway)

  reply	other threads:[~2021-04-07 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  9:21 [RFC PATCH v1 0/2] Add regression mailing list with basics for tracking Thorsten Leemhuis
2021-04-07  9:21 ` [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list Thorsten Leemhuis
2021-04-07  9:56   ` Greg KH
2021-04-07 10:51     ` Thorsten Leemhuis
2021-04-07 14:56       ` Greg KH
2021-04-07 17:53         ` Thorsten Leemhuis
2021-04-07  9:21 ` [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list Thorsten Leemhuis
2021-04-07 10:00   ` Greg KH
2021-04-07 11:21     ` Thorsten Leemhuis [this message]
2021-04-07 14:58       ` Greg KH
2021-04-08 17:31   ` Jonathan Corbet
2021-04-09 11:54     ` Thorsten Leemhuis

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=3df9566e-bb08-f1e2-7afb-a14a28d2d64f@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list' \
    /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

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).