linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Kennedy <george.kennedy@oracle.com>
To: Dmitry Vyukov <dvyukov@google.com>, shuah <shuah@kernel.org>
Cc: Cyril Hrubis <chrubis@suse.cz>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	automated-testing@yoctoproject.org, kernelci@groups.io,
	Dhaval Giani <dhaval.giani@gmail.com>,
	Jan Setje-Eilers <jan.setjeeilers@oracle.com>,
	syzkaller <syzkaller@googlegroups.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Automated-testing] syzkaller reproducers
Date: Tue, 3 Mar 2020 08:46:23 -0500	[thread overview]
Message-ID: <2d593685-b50e-ea2c-a724-818f6b149731@oracle.com> (raw)
In-Reply-To: <CACT4Y+aZ=rBZXdnrU0D-21QqSK0G3vqHU+iD=k0PhGgo3TL6rA@mail.gmail.com>



On 3/3/2020 3:45 AM, Dmitry Vyukov wrote:
> Shauh,
>
> We've added more reproducers to:
> https://github.com/dvyukov/syzkaller-repros/tree/master/linux
>
> It makes sense to pull in them to the kernel-arts repo. Not sure
> what's the most convenient way for you since it's not exactly a
> traditional "patch"? Perhaps you just copy linux/*.c files and commit?
>
> George, another throw in of 446 repros ;)

Thank you Dmitry!
George

>
>
>
> On Mon, Jan 27, 2020 at 6:08 PM George Kennedy
> <george.kennedy@oracle.com> wrote:
>>> Hi George,
>>>
>>> This was still starred in my inbox, but I never got to actually do
>>> anything with it. Thanks for pinging me. I thought that the script to
>>> extract the repros won't work for some reason and that I will need to
>>> fix it first. But turns out it's still working as-is (I wanted to
>>> submit some changes that would break it, but I never go to that as
>>> well. Good! :)).
>>>
>>> So here is a new drop in with 692 repros:
>>> https://github.com/dvyukov/syzkaller-repros/commit/6a06992209c328a3115c89c020f45b844b103573
>>> Enjoy!
>>>
>>> Yes, we have separate managers for each version, the entries in the
>>> Instances table correspond to syz-manager one-to-one:
>>> https://syzkaller.appspot.com/upstream
>>> https://syzkaller.appspot.com/linux-4.19
>>> https://syzkaller.appspot.com/android-54
>> Thank you Dmitry!
>> George
>>>
>>>
>>> On Mon, Jan 27, 2020 at 3:20 PM George Kennedy
>>> <george.kennedy@oracle.com> wrote:
>>>> Hi Dmitry,
>>>>
>>>> Re-sending this request.
>>>>
>>>> Also, how do you track the Upstream branches with Syzkaller? Do you have
>>>> a version of Syzkaller for each (i.e. 4.14, 4.19, etc)?
>>>>
>>>> Thank you,
>>>> George
>>>>
>>>> On 12/6/2019 3:06 PM, George Kennedy wrote:
>>>>> Hello Dmitry,
>>>>>
>>>>> Could we get another drop of the Syzkaller C reproducers?
>>>>>
>>>>> Wonder if we could get the drop periodically (i.e. a drop/quarter or a
>>>>> drop to match a major linux release)?
>>>>>
>>>>> Thank you,
>>>>> George


  reply	other threads:[~2020-03-03 13:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 11:46 syzkaller reproducers Dmitry Vyukov
2019-10-08 12:16 ` Dmitry Vyukov
2019-10-08 15:00   ` shuah
2019-10-11 17:38     ` shuah
2019-10-11 18:02       ` [Automated-testing] " Cyril Hrubis
2019-10-11 19:11         ` shuah
2019-10-14  8:54           ` Cyril Hrubis
2019-10-14 11:19             ` Dmitry Vyukov
2019-10-15 13:04               ` George Kennedy
2019-10-15 13:44                 ` Cyril Hrubis
2019-10-23 13:24                   ` Dmitry Vyukov
2019-12-06 20:06                 ` George Kennedy
2020-01-27 14:19                   ` George Kennedy
2020-01-27 15:26                     ` Dmitry Vyukov
2020-01-27 17:06                       ` George Kennedy
2020-03-03  8:45                         ` Dmitry Vyukov
2020-03-03 13:46                           ` George Kennedy [this message]
2020-03-13 15:59                           ` shuah
2019-10-08 16:35   ` George Kennedy
2019-10-08 12:37 ` [Automated-testing] " Richard Palethorpe
2019-10-08 12:53   ` Dmitry Vyukov
2019-10-08 13:14     ` Richard Palethorpe
2019-10-08 13:22       ` Dmitry Vyukov
2019-10-10 14:27 ` Cyril Hrubis
2019-10-10 14:30   ` 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=2d593685-b50e-ea2c-a724-818f6b149731@oracle.com \
    --to=george.kennedy@oracle.com \
    --cc=automated-testing@yoctoproject.org \
    --cc=chrubis@suse.cz \
    --cc=dan.carpenter@oracle.com \
    --cc=dhaval.giani@gmail.com \
    --cc=dvyukov@google.com \
    --cc=jan.setjeeilers@oracle.com \
    --cc=kernelci@groups.io \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=syzkaller@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 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).