linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	Arnd Bergmann <arnd@arndb.de>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] lockdep: add lockdep_cleanup_dead_cpu()
Date: Thu, 26 Sep 2024 17:45:32 -0700	[thread overview]
Message-ID: <ZvYALG8PDrcwMSUb@boqun-archlinux> (raw)
In-Reply-To: <ff9c0a7328c4ead69f9f3b37fe8746ca6a3f03b9.camel@infradead.org>

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.

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!

Regards,
Boqun

(you can refer some context here [1], in case you wonder who's this
Boqun guy and why is he doing this ;-))

[1]: https://lore.kernel.org/lkml/Zq5KmTEnalIOHf6a@boqun-archlinux/

  reply	other threads:[~2024-09-27  0:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 15:17 [PATCH v2] lockdep: add lockdep_cleanup_dead_cpu() David Woodhouse
2024-09-26 16:09 ` Boqun Feng
2024-09-26 16:37   ` David Woodhouse
2024-09-27  0:45     ` Boqun Feng [this message]
2024-09-27  8:45       ` David Woodhouse
2024-10-22 21:53 ` [tip: locking/core] lockdep: Add lockdep_cleanup_dead_cpu() tip-bot2 for David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2023-10-28 11:14 [PATCH] lockdep: add lockdep_cleanup_dead_cpu() David Woodhouse
2023-10-28 19:24 ` [PATCH v2] " David Woodhouse
2023-10-29 10:05   ` kernel test robot
2023-10-29 17:33   ` Thomas Gleixner
2023-10-29 17:47     ` David Woodhouse
2023-10-30 16:37   ` kernel test robot

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=ZvYALG8PDrcwMSUb@boqun-archlinux \
    --to=boqun.feng@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.de \
    --cc=dwmw2@infradead.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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).