From: Thomas Gleixner <tglx@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Borislav Petkov <bp@alien8.de>,
syzbot <syzbot+74de56995244fe32ffe2@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
Date: Fri, 30 Oct 2026 20:18:04 +0100 [thread overview]
Message-ID: <87jymzxaj7.ffs@fw13> (raw)
In-Reply-To: <20261029165636.GA5110@yaz-khff2.amd.com>
On Thu, Oct 29 2026 at 12:56, Yazen Ghannam wrote:
> On Wed, Oct 28, 2026 at 08:45:07PM +0100, Thomas Gleixner wrote:
> These were able to hit the new Sashiko findings.
>
> There are two separate ones.
> 1) Another deadlock.
> 2) PREEMPT_RT warning.
Grrr.
> The diff below fixes both. Though I'm not sure the if the msleep() is
> okay.
Not really.
I think I know how to fix it for real now that I understood the nasty
interaction with kernfs, but I won't come around to look into it before
Monday.
prev parent reply other threads:[~2026-10-30 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a7ec39f.5b0d2c79.2ef4ef.0002.GAE@google.com>
2026-08-17 21:14 ` [syzbot] [kernel?] general protection fault in timers_dead_cpu Thomas Gleixner
2026-08-17 22:12 ` Thomas Gleixner
2026-08-18 0:21 ` Borislav Petkov
2026-08-17 22:14 ` [PATCH] timer: Keep debugobjects state consistent in migrate_timer_list() Thomas Gleixner
2026-08-17 23:55 ` [syzbot] [kernel?] general protection fault in timers_dead_cpu Borislav Petkov
2026-08-18 0:18 ` Borislav Petkov
2026-08-18 9:09 ` Thomas Gleixner
2026-10-23 9:18 ` [PATCH] x86/mce: Serialize sysfs controls against CPU hotplug Thomas Gleixner
2026-10-28 19:45 ` [PATCH V2] " Thomas Gleixner
2026-10-29 16:56 ` Yazen Ghannam
2026-10-29 17:46 ` Borislav Petkov
2026-10-29 18:08 ` Yazen Ghannam
2026-10-29 19:02 ` Borislav Petkov
2026-10-30 19:18 ` Thomas Gleixner [this message]
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=87jymzxaj7.ffs@fw13 \
--to=tglx@kernel.org \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+74de56995244fe32ffe2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tony.luck@intel.com \
--cc=yazen.ghannam@amd.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