From: Dmitry Vyukov <dvyukov@google.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>,
syzkaller <syzkaller@googlegroups.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: monthly summary emails
Date: Sat, 23 Nov 2019 07:00:55 +0100 [thread overview]
Message-ID: <CACT4Y+ZAbRY3qNR7V7me90mv8e5-9v9YOv_McjOVZX=hqLBTVQ@mail.gmail.com> (raw)
In-Reply-To: <20191122113205.GH5604@kadam>
On Fri, Nov 22, 2019 at 12:32 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> Hi Dmitry,
>
> I help maintain drivers/staging. Would it be possible to send us a
> monthly summary of outstanding staging bugs? I never remember to check
> the website.
Hi Dan,
syzbot does not have such functionality. Maybe you seen +Eric's
emails, but that's purely manual effort at the moment. The issue to
follow for pings is: https://github.com/google/syzkaller/issues/550
But I am not sure syzkaller have any good coverage for
drivers/staging. In fact, now looking at coverage we report -- we
don't have any (except for android/{ion,ashmem}). So if you are
interested in drivers/staging quality, the first thing would be adding
syzkaller descriptions for code in drivers/staging, see:
https://github.com/google/syzkaller/blob/master/docs/syscall_descriptions.md#describing-new-system-calls
However, if the code is written in a way that makes untestable without
actual hardware, then syzbot won't help. But this also means the code
is not unit-tested and unit-testing is generally higher priority than
fuzzing (fuzzing is meant to find trickier bugs in a way that makes
them harder to debug and fix). If that's the case, then we need to
make it unit-testable/testable without hardware, which will ensure
some basic quality and will also open the road for fuzzing. Sorry, no
magic here...
Kunit may help with making code testable, see this for our recent
experiment for faking hardware:
https://groups.google.com/g/syzkaller/c/QyexLE6M3kM/m/Hwid5kk0CwAJ
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2019-11-23 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 11:32 monthly summary emails Dan Carpenter
2019-11-23 6:00 ` Dmitry Vyukov [this message]
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+ZAbRY3qNR7V7me90mv8e5-9v9YOv_McjOVZX=hqLBTVQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=ebiggers@google.com \
--cc=syzkaller-bugs@googlegroups.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).