From: Jens Axboe <axboe@kernel.dk>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+c48f34012b06c4ac67dd@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com,
Matthew Wilcox <willy@infradead.org>,
Ralph Campbell <rcampbell@nvidia.com>,
David Hildenbrand <david@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: kernel BUG at include/linux/swapops.h:LINE!
Date: Tue, 21 Jul 2020 09:11:41 -0600 [thread overview]
Message-ID: <16e40194-05ac-536b-303f-d2fd31493229@kernel.dk> (raw)
In-Reply-To: <20200721111131.bo3g6qkcvbhpupon@black.fi.intel.com>
On 7/21/20 5:11 AM, Kirill A. Shutemov wrote:
> On Mon, Jul 20, 2020 at 04:51:44PM -0700, Andrew Morton wrote:
>> On Sun, 19 Jul 2020 14:10:19 -0700 syzbot <syzbot+c48f34012b06c4ac67dd@syzkaller.appspotmail.com> wrote:
>>
>>> syzbot has found a reproducer for the following issue on:
>>>
>>> HEAD commit: 4c43049f Add linux-next specific files for 20200716
>>> git tree: linux-next
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=12c56087100000
>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c76d72659687242
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=c48f34012b06c4ac67dd
>>> compiler: gcc (GCC) 10.1.0-syz 20200507
>>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1344abeb100000
>>>
>>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>>> Reported-by: syzbot+c48f34012b06c4ac67dd@syzkaller.appspotmail.com
>>
>> Thanks.
>>
>> __handle_mm_fault
>> ->pmd_migration_entry_wait
>> ->migration_entry_to_page
>>
>> stumbled onto an unlocked page.
>>
>> I don't immediately see a cause. Perhaps Matthew's "THP prep patches",
>> perhaps something else.
>>
>> Is it possible to perform a bisection?
>
> Maybe it's related to the new lock_page_async()?
Shouldn't be used for any of those paths at all, though of course can't
rule out a bug that triggers it somehow. A bisection would be nice.
--
Jens Axboe
next prev parent reply other threads:[~2020-07-21 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 17:05 kernel BUG at include/linux/swapops.h:LINE! syzbot
2020-07-19 21:10 ` syzbot
2020-07-20 23:51 ` Andrew Morton
2020-07-21 0:21 ` Matthew Wilcox
2020-07-21 2:14 ` Matthew Wilcox
2020-07-21 11:11 ` Kirill A. Shutemov
2020-07-21 15:11 ` Jens Axboe [this message]
[not found] ` <20200723073744.5268-1-hdanton@sina.com>
2020-07-24 11:13 ` Kirill A. Shutemov
2020-07-26 16:49 ` Matthew Wilcox
2020-07-27 10:31 ` Kirill A. Shutemov
2020-07-27 12:03 ` Matthew Wilcox
2020-07-29 19:21 ` Kirill A. Shutemov
2020-07-29 19:54 ` Matthew Wilcox
2020-07-29 22:11 ` Matthew Wilcox
[not found] ` <20200727125950.12048-1-hdanton@sina.com>
2020-07-27 13:44 ` Matthew Wilcox
2021-05-08 11:24 ` [syzbot] " syzbot
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=16e40194-05ac-536b-303f-d2fd31493229@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rcampbell@nvidia.com \
--cc=syzbot+c48f34012b06c4ac67dd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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).