All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot 
	<syzbot+c91c53af67f9ebe599a337d2e70950366153b295@syzkaller.appspotmail.com>
Cc: David Miller <davem@davemloft.net>,
	Eric Biggers <ebiggers@google.com>,
	John Fastabend <john.fastabend@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>, Ozgur <ozgur@goosey.org>,
	syzkaller-bugs@googlegroups.com,
	Tom Herbert <tom@herbertland.com>,
	Tom Herbert <tom@quantonium.net>,
	Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: WARNING in strp_data_ready
Date: Thu, 28 Dec 2017 09:13:50 +0100	[thread overview]
Message-ID: <CACT4Y+YpnM-+P6OHQ5ksZtRK5zpWBBAs3i5Ypd-8VKj5oyJ1Dg@mail.gmail.com> (raw)
In-Reply-To: <94eb2c1170ce0e23ba0561621235@google.com>

On Thu, Dec 28, 2017 at 9:12 AM, syzbot
<syzbot+c91c53af67f9ebe599a337d2e70950366153b295@syzkaller.appspotmail.com>
wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+c91c53af67f9ebe599a337d2e70950366153b295@syzkaller.appspotmail.com

/\/\/\/\/\/\/\/\/\/\/\/\/\

Tom, please don't miss this part!

> Note: the tag will also help syzbot to understand when the bug is fixed.
>
> Tested on commit 5f520fc318764df800789edd202b5e3b55130613
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> Patch is attached.
> Kernel config is attached.
>
>
> ---
> There is no WARRANTY for the result, to the extent permitted by applicable
> law.
> Except when otherwise stated in writing syzbot provides the result "AS IS"
> without warranty of any kind, either expressed or implied, but not limited
> to,
> the implied warranties of merchantability and fittness for a particular
> purpose.
> The entire risk as to the quality of the result is with you. Should the
> result
> prove defective, you assume the cost of all necessary servicing, repair or
> correction.

  reply	other threads:[~2017-12-28  8:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 15:20 WARNING in strp_data_ready syzbot
2017-10-24 15:20 ` syzbot
2017-10-30 21:44 ` John Fastabend
2017-10-30 21:44   ` John Fastabend
2017-10-30 22:06   ` Tom Herbert
2017-10-30 22:06     ` Tom Herbert
2017-12-06 15:44     ` Dmitry Vyukov
2017-12-06 15:44       ` Dmitry Vyukov
2017-12-27 18:25       ` Dmitry Vyukov
2017-12-27 18:25         ` Dmitry Vyukov
2017-12-27 19:09         ` Tom Herbert
2017-12-27 19:09           ` Tom Herbert
2017-12-27 19:20           ` Dmitry Vyukov
2017-12-27 19:20             ` Dmitry Vyukov
     [not found]             ` <1164631514405294@web52j.yandex.ru>
2017-12-27 20:14               ` Dmitry Vyukov
2017-12-27 20:14                 ` Dmitry Vyukov
     [not found]                 ` <926421514406019@web43j.yandex.ru>
2017-12-28  1:19                   ` Tom Herbert
2017-12-28  1:19                     ` Tom Herbert
2017-12-28  7:54                     ` Dmitry Vyukov
2017-12-28  7:54                       ` Dmitry Vyukov
2017-12-28  8:12                       ` syzbot
2017-12-28  8:12                         ` syzbot
2017-12-28  8:13                         ` Dmitry Vyukov [this message]
2017-12-28  8:13                           ` Dmitry Vyukov
     [not found]                     ` <297161514451589@web50o.yandex.ru>
2017-12-28 16:14                       ` Tom Herbert
2017-12-28 16:14                         ` Tom Herbert
2017-12-28 16:33                         ` Dmitry Vyukov
2017-12-28 16:33                           ` Dmitry Vyukov
     [not found]                           ` <2278061514485284@web47j.yandex.ru>
2017-12-28 18:35                             ` Dmitry Vyukov
2017-12-28 18:35                               ` Dmitry Vyukov

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=CACT4Y+YpnM-+P6OHQ5ksZtRK5zpWBBAs3i5Ypd-8VKj5oyJ1Dg@mail.gmail.com \
    --to=dvyukov@google.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ozgur@goosey.org \
    --cc=syzbot+c91c53af67f9ebe599a337d2e70950366153b295@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tom@herbertland.com \
    --cc=tom@quantonium.net \
    --cc=xiyou.wangcong@gmail.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.