All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+48340bb518e88849e2e3@syzkaller.appspotmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	syzkaller-bugs@googlegroups.com
Subject: Re: dangers of bots on the mailing lists was Re: divide error in ___bpf_prog_run
Date: Wed, 17 Jan 2018 10:49:24 +0100	[thread overview]
Message-ID: <20180117094924.GA23529@amd> (raw)
In-Reply-To: <CACT4Y+ZWr9CoBqTWDW=czm29kmGYVYHvDkRiN2dp4Mz43HSTKA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

On Wed 2018-01-17 10:45:16, Dmitry Vyukov wrote:
> On Wed, Jan 17, 2018 at 10:32 AM, Pavel Machek <pavel@ucw.cz> wrote:
> > On Fri 2018-01-12 17:58:01, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> 19d28fbd306e7ae7c1acf05c3e6968b56f0d196b
> >
> > What an useful way to describe kernel version.
> >
> > Could we get reasonable subject line? 4.15-rc7: prefix would be nice
> > if it is on mainline,
> 
> Yes, I guess. I am all for useful improvements.
> What exactly is reasonable subject line? And how it can be extracted
> for an arbitrary kernel tree?

Figure something out. Everyone trying to act on your bug report will
need to find out, anyway, and searching for trees having just sha1
hash is just not funny.

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-01-17  9:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-13  1:58 divide error in ___bpf_prog_run syzbot
2018-01-14  0:16 ` Daniel Borkmann
2018-01-14 16:03   ` David Miller
2018-01-17  9:32 ` dangers of bots on the mailing lists was " Pavel Machek
2018-01-17  9:35   ` syzbot
2018-01-17  9:35   ` syzbot
2018-01-17  9:45   ` dangers of bots on the mailing lists was " Dmitry Vyukov
2018-01-17  9:49     ` Pavel Machek [this message]
2018-01-17 10:11     ` Henrique de Moraes Holschuh
2018-01-18 10:57       ` Dmitry Vyukov
2018-01-18 13:41         ` Henrique de Moraes Holschuh
2018-01-17  9:48   ` Dmitry Vyukov
2018-01-17  9:52     ` Pavel Machek
2018-01-17 10:03       ` Florian Westphal
2018-01-17  9:49   ` Daniel Borkmann
2018-01-17 11:09     ` Dmitry Vyukov
2018-01-17 20:47       ` Theodore Ts'o
2018-01-18  0:21         ` Alexei Starovoitov
2018-01-18  1:09           ` Theodore Ts'o
2018-01-18  1:18             ` Joe Perches
2018-01-18  1:46               ` Eric Biggers
2018-01-18  2:35                 ` Joe Perches
2018-01-18 13:01             ` Dmitry Vyukov
2018-01-18 13:06               ` Dmitry Vyukov
2018-01-18 14:05               ` Greg Kroah-Hartman
2018-01-22 13:31                 ` Dmitry Vyukov
2018-01-18 14:10               ` Guenter Roeck
2018-01-22  8:08                 ` Dmitry Vyukov
2018-01-18 13:10       ` Dmitry Vyukov
2018-01-18 14:46         ` Daniel Borkmann

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=20180117094924.GA23529@amd \
    --to=pavel@ucw.cz \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+48340bb518e88849e2e3@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.