LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: syzbot <syzbot+4fd0c066d82852499145@syzkaller.appspotmail.com>,
	Jan Kara <jack@suse.cz>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs@googlegroups.com,
	Al Viro <viro@zeniv.linux.org.uk>,
	zwisler@kernel.org
Subject: Re: WARNING in get_unlocked_entry
Date: Wed, 31 Oct 2018 20:20:44 +0100	[thread overview]
Message-ID: <CACT4Y+Y1BFaasXeW_yKqXaoZJ3btFpFNV_WY5ZrU4rhPmZcyZg@mail.gmail.com> (raw)
In-Reply-To: <20181031191827.GN10491@bombadil.infradead.org>

On Wed, Oct 31, 2018 at 8:18 PM, Matthew Wilcox <willy@infradead.org> wrote:
> On Wed, Oct 31, 2018 at 10:46:19AM +0100, Dmitry Vyukov wrote:
>> On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox <willy@infradead.org> wrote:
>> > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote:
>> >> syzbot found the following crash on:
>> >>
>> >> HEAD commit:    4b42745211af Merge tag 'armsoc-soc' of git://git.kernel.or..
>> >> git tree:       upstream
>> >> console output: https://syzkaller.appspot.com/x/log.txt?x=1187d06d400000
>> >> kernel config:  https://syzkaller.appspot.com/x/.config?x=93932074d01b4a5
>> >> dashboard link: https://syzkaller.appspot.com/bug?extid=4fd0c066d82852499145
>> >> compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
>> >>
>> >> Unfortunately, I don't have any reproducer for this crash yet.
>> >
>> > Hmmpf.  Would have been nice if syzbot had caught this during its tests
>> > of the -next tree ...
>>
>> What -next tree do you mean? If it satisfies the criteria we can add it:
>> https://github.com/google/syzkaller/issues/592
>
> I meant linux-next, as in the merge of everybody's -next trees.  Reading
> that bug, it seems outside your scope for now ;-(


We do test linux-next:
https://syzkaller.appspot.com/#managers
But this crash happened only once across all trees and machines. So it
just looks too elusive (subtle race?) to be reliably spotted in
linux-next.

      reply	other threads:[~2018-10-31 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 15:00 syzbot
2018-10-31  3:18 ` Matthew Wilcox
2018-10-31  9:45   ` Dmitry Vyukov
2018-10-31  9:46   ` Dmitry Vyukov
2018-10-31 19:18     ` Matthew Wilcox
2018-10-31 19:20       ` 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+Y1BFaasXeW_yKqXaoZJ3btFpFNV_WY5ZrU4rhPmZcyZg@mail.gmail.com \
    --to=dvyukov@google.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+4fd0c066d82852499145@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=zwisler@kernel.org \
    --subject='Re: WARNING in get_unlocked_entry' \
    /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

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).