From: Eric Sandeen <sandeen@sandeen.net>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Eric Biggers <ebiggers3@gmail.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Dave Chinner <david@fromorbit.com>,
Brian Foster <bfoster@redhat.com>,
syzbot <syzbot+568245b88fbaedcb1959@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: task hung in xlog_grant_head_check
Date: Mon, 11 Jun 2018 09:35:08 -0500 [thread overview]
Message-ID: <46be4dcc-15e5-1482-042b-a0bcdb0fa56b@sandeen.net> (raw)
In-Reply-To: <CACT4Y+b4+o86Aud9K3m1HWhqsbNoyvEfW+53R2WV=Redi6Cwew@mail.gmail.com>
On 6/11/18 8:20 AM, Dmitry Vyukov wrote:
> On Wed, May 23, 2018 at 8:01 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
...
>> As an aside, I wonder how much coverage of the V5 format code syzkaller
>> /has/
>> achieved; that would be another useful datapoint google could provide - if
>> syzkaller is in fact traversing the V5 codepaths and isn't turning anything
>> up, that'd be pretty useful to know.
>
> Hi Eric,
>
> The current syzbot kernel code coverage is available here:
> https://storage.googleapis.com/syzkaller/cover/upstream.html#9c73bb525fc1def86e67f5039ab97d8f48062621
Here is an example of an informative, useful, and efficient presentation of
code coverage:
http://ltp.sourceforge.net/coverage/lcov/output/index.html
Thanks,
-Eric
next prev parent reply other threads:[~2018-06-11 14:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 17:55 INFO: task hung in xlog_grant_head_check syzbot
2018-05-22 12:31 ` Brian Foster
2018-05-22 22:26 ` Dave Chinner
2018-05-22 22:52 ` Eric Biggers
2018-05-23 4:47 ` Dave Chinner
2018-05-23 7:44 ` Darrick J. Wong
2018-05-23 16:20 ` Eric Biggers
2018-05-23 18:01 ` Eric Sandeen
2018-05-23 23:41 ` Bugs involving maliciously crafted file system Theodore Y. Ts'o
2018-05-24 0:49 ` Dave Chinner
2018-05-24 0:59 ` Theodore Y. Ts'o
2018-05-24 3:55 ` Dave Chinner
2018-05-24 13:16 ` Eric Sandeen
2018-05-30 19:41 ` Eric W. Biederman
2018-05-30 20:51 ` Matthew Garrett
2018-06-11 13:11 ` Dmitry Vyukov
2018-05-26 17:12 ` Dmitry Vyukov
2018-05-26 20:24 ` Theodore Y. Ts'o
2018-06-11 13:07 ` Dmitry Vyukov
2018-06-11 13:33 ` Theodore Y. Ts'o
2018-06-15 9:32 ` Dmitry Vyukov
2018-06-11 13:20 ` INFO: task hung in xlog_grant_head_check Dmitry Vyukov
2018-06-11 14:35 ` Eric Sandeen [this message]
2018-05-23 23:35 ` Dave Chinner
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=46be4dcc-15e5-1482-042b-a0bcdb0fa56b@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+568245b88fbaedcb1959@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.