All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Potapenko <glider@google.com>
To: Hillf Danton <hdanton@sina.com>, Al Viro <viro@zeniv.linux.org.uk>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Matthew Wilcox <willy@infradead.org>,
	syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Tue, 13 Dec 2022 12:05:52 +0100	[thread overview]
Message-ID: <CAG_fn=VbTqF8CrBXC=F7jwy=Yr=ExGQcGvSzMsixmF=2vu285A@mail.gmail.com> (raw)
In-Reply-To: <20221213041225.3461-1-hdanton@sina.com>

On Tue, Dec 13, 2022 at 5:12 AM Hillf Danton <hdanton@sina.com> wrote:
>
> On 13 Dec 2022 03:36:23 +0000 Al Viro <viro@zeniv.linux.org.uk>
> > On Tue, Dec 13, 2022 at 09:47:16AM +0800, Hillf Danton wrote:
> >
> > > > maintainer time is expensive.  So by not improving syzbot in a way
> > > > that really shouldn't be all that difficult, the syzbot maintainers is
> > > > disrespectiving the time of the upstream maintainers.
> > >
> > > Are upstream maintainers prefering to spend weeks and months creating
> > > ext4 beatles for example over taking a couple of hours scanning the
> > > syzbot reports like this one? Why does the bot kick you if you have a
> > > clean butt? Why are usb people irrelevant in this case?
> >
> > And to continue with the rethorical questions: has anyone bothered to
> > inform you that you are an obnoxious cunt?
>
> When did cunt go in to your mind? And How?
> >
> > *plonk*


I think it's time to take a step back now and try to keep the
discussion constructive.
It's really about bots and automation, no need to engage in personalities.

I myself am not involved in improving syzbot, but as a bystander let
me assure you that the folks do take the feedback seriously and
actually have interest in improving the experience for the upstream
maintainers.



> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/20221213041225.3461-1-hdanton%40sina.com.



-- 
Alexander Potapenko
Software Engineer

Google Germany GmbH
Erika-Mann-Straße, 33
80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg

  reply	other threads:[~2022-12-13 11:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221211002908.2210-1-hdanton@sina.com>
2022-12-11  2:30 ` [syzbot] WARNING in do_mkdirat syzbot
2022-12-11  2:52   ` Al Viro
2022-12-11  7:56     ` Hillf Danton
2022-12-11  8:39       ` Al Viro
2022-12-11 10:22         ` Hillf Danton
2022-12-11 15:46           ` Matthew Wilcox
2022-12-11 20:54             ` Al Viro
2022-12-12  3:29             ` Hillf Danton
2022-12-12 18:58               ` Theodore Ts'o
2022-12-12 19:29                 ` Marco Elver
2022-12-13  1:44                   ` Al Viro
2022-12-13  2:25                     ` Hillf Danton
2022-12-16 15:48                     ` Aleksandr Nogikh
2022-12-29 21:17                       ` Eric Biggers
2022-12-31 16:57                         ` Theodore Ts'o
2022-12-31 17:03                           ` Randy Dunlap
2023-01-03 13:36                           ` Aleksandr Nogikh
2022-12-13  1:47                 ` Hillf Danton
2022-12-13  3:36                   ` Al Viro
2022-12-13  4:12                     ` Hillf Danton
2022-12-13 11:05                       ` Alexander Potapenko [this message]
     [not found] <20221215235133.1097-1-hdanton@sina.com>
2022-12-16  7:53 ` syzbot
     [not found] <20221210011440.2050-1-hdanton@sina.com>
2022-12-10  7:24 ` syzbot
2022-12-03 14:52 syzbot
2022-12-04  1:04 ` Hillf Danton
2022-12-09 19:50 ` syzbot
2022-12-09 19:57   ` Matthew Wilcox
2022-12-10 18:06 ` syzbot

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='CAG_fn=VbTqF8CrBXC=F7jwy=Yr=ExGQcGvSzMsixmF=2vu285A@mail.gmail.com' \
    --to=glider@google.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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.