From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: syzbot <syzbot+b577bc624afda52c78de@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, brauner@kernel.org, daniel@iogearbox.net,
david@redhat.com, ebiederm@xmission.com,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, yhs@fb.com, linux-mm@kvack.org,
Christoph Hellwig <hch@infradead.org>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] BUG: sleeping function called from invalid context in __vmalloc_node_range
Date: Mon, 20 Jun 2022 12:19:50 +0200 [thread overview]
Message-ID: <YrBJxrbq8Yvrpshj@linutronix.de> (raw)
In-Reply-To: <000000000000e57c2b05e1c03426@google.com>
#syz fix: mm/page_alloc: protect PCP lists with a spinlock
#syz dup: BUG: sleeping function called from invalid context in relay_open_buf
The version of the patch above in next-20220614 is buggy leading to the
report below. The version in next-20220620 is fine. Not sure how to tell
syz bot this…
On 2022-06-18 15:15:20 [-0700], syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 35d872b9ea5b Add linux-next specific files for 20220614
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=155b0d10080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d7bf2236c6bb2403
> dashboard link: https://syzkaller.appspot.com/bug?extid=b577bc624afda52c78de
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+b577bc624afda52c78de@syzkaller.appspotmail.com
>
> BUG: sleeping function called from invalid context at mm/vmalloc.c:2980
…
> Preemption disabled at:
> [<ffffffff81bc76f5>] rmqueue_pcplist mm/page_alloc.c:3813 [inline]
> [<ffffffff81bc76f5>] rmqueue mm/page_alloc.c:3858 [inline]
> [<ffffffff81bc76f5>] get_page_from_freelist+0x455/0x3a20 mm/page_alloc.c:4293
Sebastian
next parent reply other threads:[~2022-06-20 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e57c2b05e1c03426@google.com>
2022-06-20 10:19 ` Sebastian Andrzej Siewior [this message]
2022-06-20 11:24 ` Aleksandr Nogikh
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=YrBJxrbq8Yvrpshj@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+b577bc624afda52c78de@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yhs@fb.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