public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	syzbot <syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Alexandre Chartre <alexandre.chartre@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [syzbot] upstream boot error: WARNING in __context_tracking_enter
Date: Wed, 10 Nov 2021 10:08:45 +0100	[thread overview]
Message-ID: <YYuMHchsq7UKwiD8@elver.google.com> (raw)
In-Reply-To: <CACT4Y+ZaFKB6xd9BiPjYsE+13GJb3d_4aRTkB8xrNMaexpLaFA@mail.gmail.com>

On Tue, Apr 13, 2021 at 07:14AM +0200, Dmitry Vyukov wrote:
[...]
> Hi Russell,
> 
> Does Mark's comment make sense to you?
> lockdep_assert_preemption_disabled() also checks "&&
> this_cpu_read(hardirqs_enabled)", so is it that we also need hardirq's
> disabled around user_enter/exit?
> This issue currently prevents ARM boot on syzbot.

We've disabled lockdep on syzbot's arm32 instance now as that instance had
been dead since March:
https://github.com/google/syzkaller/commit/be386ae8800e02b4a9a3239c9565e9d40e253c84

It's running again. There may be an influx of new bugs.

Thanks,
-- Marco

      reply	other threads:[~2021-11-10  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  9:44 [syzbot] upstream boot error: WARNING in __context_tracking_enter syzbot
2021-03-19  9:54 ` Dmitry Vyukov
2021-03-19 10:10   ` Russell King - ARM Linux admin
2021-03-22 17:22     ` Mark Rutland
2021-04-13  5:14       ` Dmitry Vyukov
2021-11-10  9:08         ` Marco Elver [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=YYuMHchsq7UKwiD8@elver.google.com \
    --to=elver@google.com \
    --cc=alexandre.chartre@oracle.com \
    --cc=arnd@arndb.de \
    --cc=dvyukov@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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