From: Shuah Khan <skhan@linuxfoundation.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] Wrapper for Syzkaller reproducers
Date: Tue, 9 Jun 2020 15:39:34 -0600 [thread overview]
Message-ID: <8b3cbf25-83ad-42da-f3ec-e2bafdfff97c@linuxfoundation.org> (raw)
In-Reply-To: <20200609195851.GA29515@x230>
On 6/9/20 1:58 PM, Petr Vorel wrote:
> Hi Shuah,
>
> ...
>>> I don't have any particular comments.
>>> I assume Richard tested it and it works. if so, it's fine with me :)
>>> I don't have any concrete plans to use this at the moment. We have a
>>> corpus of reproducers in syzkaller format and we can run these. This
>>> should be more useful for kernel continuous integration systems and
>>> distro testing.
>
>> Right. That is what I was thinking that this is more relevant for kernel
>> developers, CI and distros.
>
>> Richard, Please send the patch for linux-arts to me once Petr gives it a
>> try and I will apply it.
> NOTE: this patch is for LTP. But maybe I miss something (some other patch for
> linux-arts I overlooked).
>
Possibly I misread the
V3:
+ Updated linux-arts commit (thanks Dmitry and Shuah for updating those!)
+ Fixed AC macro
If this patch doesn't intend to update syzkaller-repo, there is
nothing to do for linux-arts. I thought that this patch is for
Dmitry's syzkaller repo I update from and looking get this into
linux-arts directly.
Since this is LTP patch, ignore my comments. Sorry for the noise.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-06-09 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 11:34 [LTP] [PATCH v3] Wrapper for Syzkaller reproducers Richard Palethorpe
2020-06-09 16:59 ` Petr Vorel
2020-06-09 17:10 ` Shuah Khan
2020-06-09 17:15 ` Dmitry Vyukov
2020-06-09 17:20 ` Shuah Khan
2020-06-09 19:58 ` Petr Vorel
2020-06-09 21:39 ` Shuah Khan [this message]
2020-06-10 7:18 ` Richard Palethorpe
2020-06-10 7:27 ` Petr Vorel
2020-06-15 7:26 ` Li Wang
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=8b3cbf25-83ad-42da-f3ec-e2bafdfff97c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=ltp@lists.linux.it \
/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