From: Phil Auld <pauld@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <vschneid@redhat.com>
Subject: [PATCH] cpuhp: make target_store() a nop when target == state
Date: Mon, 23 May 2022 10:47:28 -0400 [thread overview]
Message-ID: <20220523144728.32414-1-pauld@redhat.com> (raw)
writing the current state back into hotplug/target calls cpu_down()
which will set cpu dying even when it isn't and then nothing will
ever clear it. A stress test that reads values and writes them back
for all cpu device files in sysfs will trigger the BUG() in
select_fallback_rq once all cpus are marked as dying.
kernel/cpu.c::target_store()
...
if (st->state < target)
ret = cpu_up(dev->id, target);
else
ret = cpu_down(dev->id, target);
cpu_down() -> cpu_set_state()
bool bringup = st->state < target;
...
if (cpu_dying(cpu) != !bringup)
set_cpu_dying(cpu, !bringup);
Make this safe by catching the case where target == state
and bailing early.
Signed-off-by: Phil Auld <pauld@redhat.com>
---
Yeah, I know... don't do that. But it's still messy.
!< != >
kernel/cpu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index d0a9aa0b42e8..8a71b1149c60 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -2302,6 +2302,9 @@ static ssize_t target_store(struct device *dev, struct device_attribute *attr,
return -EINVAL;
#endif
+ if (target == st->state)
+ return count;
+
ret = lock_device_hotplug_sysfs();
if (ret)
return ret;
--
2.18.0
next reply other threads:[~2022-05-23 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:47 Phil Auld [this message]
2022-05-24 15:11 ` [PATCH] cpuhp: make target_store() a nop when target == state Valentin Schneider
2022-05-24 16:39 ` Phil Auld
2022-05-25 9:48 ` Valentin Schneider
2022-05-25 13:31 ` Phil Auld
2022-05-25 15:09 ` Valentin Schneider
2022-05-25 15:11 ` Phil Auld
2022-05-24 19:37 ` Phil Auld
2022-05-25 9:48 ` Valentin Schneider
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=20220523144728.32414-1-pauld@redhat.com \
--to=pauld@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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