From: Dmitry Vyukov <dvyukov@google.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: WireGuard secure network tunnel
Date: Thu, 19 Dec 2019 11:49:23 +0100 [thread overview]
Message-ID: <CACT4Y+YfBDvQHdK24ybyyy5p07MXNMnLA7+gq9axq-EizN6jhA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qUWr69o0r+Mtm8tRSeQq3P780DhWAhpJkNWBfZ+J5OYA@mail.gmail.com>
On Thu, Dec 19, 2019 at 11:11 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> On Thu, Dec 19, 2019 at 11:07 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > On Thu, Dec 19, 2019 at 10:35 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> > That's exciting about syzcaller having at it with WireGuard. Is there
> > some place where I can "see" it fuzzing WireGuard, or do I just wait
> > for the bug reports to come rolling in?
>
> Ahh, found it: https://storage.googleapis.com/syzkaller/cover/ci-upstream-net-kasan-gce.html
> Looks like we're at 1% and counting. :)
Yes, that's it. But that's mostly stray coverage.
wg_netdevice_notification I guess mostly because it tested _other_ device types.
And a bit of netlink because it sends random garbage into netlink.
For netlink part it would require something along these lines:
https://github.com/google/syzkaller/blob/master/sys/linux/socket_netlink_generic_devlink.txt
https://github.com/google/syzkaller/blob/master/sys/linux/socket_netlink_crypto.txt
https://github.com/google/syzkaller/blob/master/sys/linux/socket_netlink_generic_fou.txt
https://github.com/google/syzkaller/blob/master/sys/linux/socket_netlink_generic_seg6.txt
And for device setup, harder to say. Either pre-create one here:
https://github.com/google/syzkaller/blob/79b211f74b08737aeb4934c6ff69a263b3c38013/executor/common_linux.h#L668
or teach it how to create them on the fly or both or something else.
Probably some wire packet formats here:
https://github.com/google/syzkaller/blob/79b211f74b08737aeb4934c6ff69a263b3c38013/sys/linux/vnet.txt
next prev parent reply other threads:[~2019-12-19 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 23:27 [PATCH net-next v2] net: WireGuard secure network tunnel Jason A. Donenfeld
2019-12-09 1:52 ` David Miller
2019-12-09 10:07 ` Jason A. Donenfeld
2019-12-18 10:12 ` Dmitry Vyukov
2019-12-18 10:57 ` Jason A. Donenfeld
2019-12-18 11:37 ` Dmitry Vyukov
2019-12-18 11:50 ` Jason A. Donenfeld
2019-12-19 9:35 ` Dmitry Vyukov
2019-12-19 10:07 ` Jason A. Donenfeld
2019-12-19 10:11 ` Jason A. Donenfeld
2019-12-19 10:49 ` Dmitry Vyukov [this message]
2019-12-19 10:53 ` Jason A. Donenfeld
2019-12-19 11:18 ` Dmitry Vyukov
2019-12-19 11:38 ` Jason A. Donenfeld
2019-12-19 14:30 ` Dmitry Vyukov
2019-12-19 10:42 ` Dmitry Vyukov
2019-12-19 10:50 ` Jason A. Donenfeld
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+YfBDvQHdK24ybyyy5p07MXNMnLA7+gq9axq-EizN6jhA@mail.gmail.com \
--to=dvyukov@google.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).