linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.3-rc2
Date: Tue, 14 Mar 2023 13:01:27 +0100	[thread overview]
Message-ID: <CAMj1kXHC+UCaWLRrujEJeqVaQ_4Wn3dQ+Mq+1ryQj6C=Qsb53w@mail.gmail.com> (raw)
In-Reply-To: <20230314114018.GF1845660@hirez.programming.kicks-ass.net>

On Tue, 14 Mar 2023 at 12:40, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Tue, Mar 14, 2023 at 12:18:33PM +0100, Frederic Weisbecker wrote:
> > How does the following look like as a culprit?
> >
> > 62b95a7b44d1 (ARM: 9282/1: vfp: Manipulate task VFP state with softirqs disabled)
>
> Ooh yeah, that asm implementation of local_bh_{dis,en}able completely
> miss out on the lockdep state tracking. Also I think it breaks RCU, note
> how __local_bh_disable_ip() explicitly does rcu_read_lock() for the
> first bh-disable.
>

Thanks a lot for the diagnosis, doctor :-)

I may need some hand holding getting this fixed - probably better to
run the C implementations wherever feasible, right?

  reply	other threads:[~2023-03-14 12:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 23:45 Linux 6.3-rc2 Linus Torvalds
2023-03-13  8:11 ` Build regressions/improvements in v6.3-rc2 Geert Uytterhoeven
2023-03-13  8:16   ` Geert Uytterhoeven
2023-03-13  9:08 ` HID: Stable backport request (all viable versions) Lee Jones
2023-03-13 10:51   ` Greg KH
2023-03-13 15:53 ` Linux 6.3-rc2 Guenter Roeck
2023-03-13 18:21   ` Linus Torvalds
2023-03-13 20:30     ` Guenter Roeck
2023-03-13 22:16       ` Linus Torvalds
2023-03-13 22:49         ` Guenter Roeck
2023-03-13 23:11     ` Frederic Weisbecker
2023-03-13 23:17       ` Linus Torvalds
2023-03-13 23:25         ` Frederic Weisbecker
2023-03-14  0:52       ` Guenter Roeck
2023-03-14 11:18         ` Frederic Weisbecker
2023-03-14 11:40           ` Peter Zijlstra
2023-03-14 12:01             ` Ard Biesheuvel [this message]
2023-03-14 12:27               ` Peter Zijlstra
2023-03-14 14:40           ` Guenter Roeck
2023-03-14 16:16           ` Guenter Roeck
2023-03-19 14:06   ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-14 14:11     ` Linux regression tracking #update (Thorsten Leemhuis)

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='CAMj1kXHC+UCaWLRrujEJeqVaQ_4Wn3dQ+Mq+1ryQj6C=Qsb53w@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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).