lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fd290c7237ff014876db92c063772903fef7079c.camel@infradead.org>
Date: Fri, 27 Sep 2024 09:45:07 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Peter Zijlstra
 <peterz@...radead.org>,  Ingo Molnar <mingo@...hat.com>, Will Deacon
 <will@...nel.org>, Waiman Long <longman@...hat.com>, Kent Overstreet
 <kent.overstreet@...ux.dev>, Arnd Bergmann <arnd@...db.de>, Sebastian
 Andrzej Siewior <bigeasy@...utronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] lockdep: add lockdep_cleanup_dead_cpu()

On Thu, 2024-09-26 at 17:45 -0700, Boqun Feng wrote:
> On Thu, Sep 26, 2024 at 05:37:12PM +0100, David Woodhouse wrote:
> > On Thu, 2024-09-26 at 09:09 -0700, Boqun Feng wrote:
> > > 
> > > I won't call this a "perfectly harmless bug", safe_halt() also contains
> > > tracepoints, which are not supposed to work in offline path IIUC, for
> > > example, you may incorrectly use RCU when RCU is not watching, that
> > > could mean reading garbage memory (surely it won't crash the system, but
> > > I hope I never need to debug such a system ;-)).
> > > 
> > > Otherwise this patch looks good to me. Thanks!
> > 
> > Apart from the fact that I can't count. Apparently I got up to v3 of it
> > last time, so this one should have been v4. I just mostly forgot all
> > about it, and found it lying around in a git tree a year later, and it
> > still seemed relevant. 
> 
> My point is calling a non-noinstr function in the offline path is not a
> "perfectly harmless" bug, it can cause serious results, so that line in
> the commit log is not true. Of course, lockdep should handle buggy code
> gracefully, but buggy code is still buggy code.

As you wish. It was very much *less* harmful than a triple-fault, and I
would at least have left something in the commit comment about lockdep
making the user-visible symptoms much worse (and hard to debug; that's
a few days of my life I want back!) — but your point is valid, and it's
not a hill to die on.

> Anyway, I've taken it into my tree (I removed the "perfectly harmless
> bug" part because of the reason above):
>         
>         git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git lockdep-for-tip
> 
> and will send it in a PR to tip around -rc2 to -rc4, so it will goes
> into v6.13 if things went well.
>
> Feel free to send a new version, if the one in my tree needs some
> changes. Again, thanks for the patch!

I think it'll do. Thanks for picking it up.

Download attachment "smime.p7s" of type "application/pkcs7-signature" (5965 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ