From: Dmitry Vyukov <dvyukov@google.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Peter Xu <peterx@redhat.com>, Peter Shier <pshier@google.com>,
syzkaller <syzkaller@googlegroups.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: syzkaller for uffd-wp
Date: Mon, 11 Nov 2019 11:28:49 +0100 [thread overview]
Message-ID: <CACT4Y+Y6CSG7fzOV7BTx3JQ8SKGy8iPyUggGUUv8A0JRhpkU7g@mail.gmail.com> (raw)
In-Reply-To: <20191031084944.GA21077@redhat.com>
On Thu, Oct 31, 2019 at 9:49 AM Andrea Arcangeli <aarcange@redhat.com> wrote:
>
> Hi Dmitry,
>
> would it be possible to grill the uffd-wp patchset with syzkaller?
> It'd be nice if we can detect bugs before it gets merged.
>
> Peter posted it upstream, but we can provide a kernel git tree to
> pull. To fuzzy you likely need to add the new UFFD_WP feature flag and
> registration options to the fuzzer.
>
> Thanks,
> Andrea
+syzkaller, linux-fsdevel
[getting through backlog after OSS/ELC/LSS]
Hi Andrea,
I won't have time for this in the near future unfortunately.
But if you (or anybody on the lists) are interested in providing
better testing for uffd, we have docs on how to extend syzkaller:
https://github.com/google/syzkaller/blob/master/docs/syscall_descriptions.md#describing-new-system-calls
You may also look at the past changes adding new syscall descriptions
and we have help provided on the syzkaller@ mailing list.
Generally, the core syzkaller team (<1 person overall) can't become
experts and describe thousands of subsystems in a dozen of OSes.
parent reply other threads:[~2019-11-11 10:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191031084944.GA21077@redhat.com>]
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+Y6CSG7fzOV7BTx3JQ8SKGy8iPyUggGUUv8A0JRhpkU7g@mail.gmail.com \
--to=dvyukov@google.com \
--cc=aarcange@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=pshier@google.com \
--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).