From: Will Deacon <will@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+0b036374a865ba0efa8e@syzkaller.appspotmail.com>,
kernel-team@android.com,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [syzbot] BUG: soft lockup in do_wp_page (4)
Date: Thu, 25 Mar 2021 18:20:47 +0000 [thread overview]
Message-ID: <20210325182046.GA15860@willie-the-truck> (raw)
In-Reply-To: <CACT4Y+a4S-oXsjgwDh3SmERqKFF1QbapvX6NiSpn51KRtqvTiQ@mail.gmail.com>
On Thu, Mar 18, 2021 at 08:34:16PM +0100, Dmitry Vyukov wrote:
> On Thu, Mar 18, 2021 at 8:31 PM syzbot
> <syzbot+0b036374a865ba0efa8e@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: bf152b0b Merge tag 'for_linus' of git://git.kernel.org/pub..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17d5264ed00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=2c9917c41f0bc04b
> > dashboard link: https://syzkaller.appspot.com/bug?extid=0b036374a865ba0efa8e
> > userspace arch: arm64
> >
> > 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+0b036374a865ba0efa8e@syzkaller.appspotmail.com
> >
> > watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor.1:3684]
>
> +Will, arm
>
> If I am reading this commit correctly, this is caused by:
>
> commit cae118b6acc309539b33339e846cbb19187c164c
> Author: Will Deacon
> Date: Wed Mar 3 13:49:27 2021 +0000
> arm64: Drop support for CMDLINE_EXTEND
>
> syzbot passes lots of critical things in CONFIG_CMDLINE:
> https://github.com/google/syzkaller/blob/c3c81c94865791469d376eba84f4a2d7763d3f71/dashboard/config/linux/upstream-arm64-kasan.config#L495
> but also wants the bootloader args to be appended.
> What is the way to do it now?
For now, there isn't a way to do it with CONFIG_CMDLINE, so I think you can
either:
* Revert my patch for your kernels
* Pass the arguments via QEMU's -append option
* Take a look at one of the series which should hopefully add this
functionality back (but with well-defined semantics) [1] [2]
Sorry for the nuisance; I did try to fix this [3] but it's a bit of a
mess.
Will
[1] https://lore.kernel.org/linux-arch/cover.1614705851.git.christophe.leroy@csgroup.eu/
[2] https://lore.kernel.org/linux-mips/20210308235319.2988609-2-danielwa@cisco.com/#t
[3] https://lore.kernel.org/r/20210225125921.13147-1-will@kernel.org
next prev parent reply other threads:[~2021-03-25 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 19:31 syzbot
2021-03-18 19:34 ` Dmitry Vyukov
2021-03-25 18:20 ` Will Deacon [this message]
2021-03-25 18:34 ` Dmitry Vyukov
2021-03-25 19:08 ` Dmitry Vyukov
2021-03-25 19:10 ` Will Deacon
2021-03-25 19:24 ` Dmitry Vyukov
2021-03-25 19:29 ` Will Deacon
2021-09-17 7:32 ` Dmitry Vyukov
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=20210325182046.GA15860@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+0b036374a865ba0efa8e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox