From: Frederic Weisbecker <frederic@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] kthread fix
Date: Thu, 29 Oct 2026 16:25:26 +0100 [thread overview]
Message-ID: <auNlZtFskpC1ijA-@localhost.localdomain> (raw)
Hi Linus,
The following changes since commit c03c1a14507dfaf8b856c2608f9ac216021fc222:
Linux 7.3 (2026-10-18 13:14:58 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git tags/kthread-fix-for-linus
for you to fetch changes up to 78ff77ded78f2d3d6040705a3ab5a83cc45275e3:
kthread: Fall back when no preferred housekeeping CPU is online (2026-10-25 19:53:54 +0100)
----------------------------------------------------------------
Fix a bug where dynamic CPU isolation through cpuset isolated partitions
can move a kthread out of the housekeeping range. For example in a
system with 3 CPUs:
_ kthread K has preferred affinity to CPUs 1 et 2 and is affine to them
_ CPU 1 goes offline
_ An isolated cpuset partition is created on CPU 2 (so the only
remaining online housekeeper is CPU 0)
_ K is affine to CPU 2 but this CPU is offline so it fails and goes back
to its previous affinity where only CPU 3 is online. Yet it is
isolated.
The fix makes sure the fallback affinity is always a set of online
housekeeper.
----------------------------------------------------------------
Avi Weiss (1):
kthread: Fall back when no preferred housekeeping CPU is online
kernel/kthread.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks.
next reply other threads:[~2026-10-29 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 15:25 Frederic Weisbecker [this message]
2026-10-29 17:57 ` Linus Torvalds
2026-10-30 0:11 ` Frederic Weisbecker
2026-10-29 18:29 ` pr-tracker-bot
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=auNlZtFskpC1ijA-@localhost.localdomain \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®