public inbox for [email protected]
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Eric Biggers <[email protected]>,
	[email protected], [email protected],
	[email protected],
	syzbot
	<[email protected]>
Subject: Re: [syzbot] Monthly io-uring report
Date: Mon, 27 Mar 2023 22:21:02 +0200	[thread overview]
Message-ID: <CANp29Y5kn4tgRKUwkfxoMHxESX=FC0GU4Yu-et45bh_MWBzviA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Mon, Mar 27, 2023 at 10:00 PM Jens Axboe <[email protected]> wrote:
>
> On 3/27/23 1:56 PM, Eric Biggers wrote:
> > On Mon, Mar 27, 2023 at 01:25:14PM -0600, Jens Axboe wrote:
> >> On 3/27/23 1:21?PM, Eric Biggers wrote:
> >>> Thanks for getting syzbot to classify reports by subsystem and send these
> >>> reminders!  These should be very helpful over time.
> >>>
> >>> One thing that is missing in these reminders is a mention of how to change the
> >>> subsystem of miscategorized bugs.  Yes, it's in https://goo.gl/tpsmEJ halfway
> >>> down the page, but it's not obvious.
> >>>
> >>> I think adding something like "See https://goo.gl/tpsmEJ#subsystems for how to
> >>> change the subsystem of miscategorized reports" would be helpful.  Probably not
> >>> in all syzbot emails, but just in these remainder emails.

That makes sense, thanks!
FWIW We can also add a subsystem-changing command that could be sent
just as a reply to such reminder email, so that there's no need to go
to the per-bug threads.

> >>
> >> I did go poke, it is listed off the reports too. But it'd be really
> >> handy if you could do this on the web page. When I see a report like
> >> that that's not for me, I just archive it. And like any chatter with
> >> syzbot, I have to look up what to reply to it every time. It'd be a lot
> >> easy if I could just click on that page to either mark as invalid
> >> (providing the info there) or move it to another subsystem.
> >>
> >
> > Well, one problem that syzbot has to deal with is that to meet the kernel
> > community's needs, it can't require authentication to issue commands.
> >
> > I understand that the current email-only interface, where all commands are Cc'ed
> > to the syzkaller-bug mailing list, makes that not a complete disaster currently.
> >
> > I'd imagine that if anyone could just go to a web page and mess around with bug
> > statuses with no authentication, that might be more problematic.
>
> What prevents anyone from just sending an email to the syzbot issue email
> and modifying it?
>
> I love using email as it's easier when you're replying anyway, but the
> problem is that I can never remember the magic incantations that I need
> to send it. So I invariably click the link ANYWAY to find out what to
> reply, and now it's more hassle using email. Maybe we can solve this by
> making the email footer actually contain the common responses? Then
> I would not have to click, switch desktops, scroll to find, copy part
> of it, switch desktops, paste into email, open terminal to generate
> the rest, switch back to email, paste in, click send. It really isn't
> a very pleasurable experience.

Thanks for the feedback and the idea!
It would indeed be much easier if we listed some sample commands at the bottom.

>
> --
> Jens Axboe
>
>

      reply	other threads:[~2023-03-27 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 11:01 [syzbot] Monthly io-uring report syzbot
2023-03-27 18:23 ` Jens Axboe
2023-03-27 19:12   ` Aleksandr Nogikh
2023-03-27 19:20     ` Jens Axboe
2023-03-27 20:12       ` Aleksandr Nogikh
2023-03-27 19:21 ` Eric Biggers
2023-03-27 19:25   ` Jens Axboe
2023-03-27 19:56     ` Eric Biggers
2023-03-27 20:00       ` Jens Axboe
2023-03-27 20:21         ` Aleksandr Nogikh [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='CANp29Y5kn4tgRKUwkfxoMHxESX=FC0GU4Yu-et45bh_MWBzviA@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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