public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samir M <samir@linux.ibm.com>
To: paulmck@kernel.org
Cc: Shrikanth Hegde <sshegde@linux.ibm.com>,
	Tejun Heo <tj@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, RCU <rcu@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org, Boqun Feng <boqun@kernel.org>
Subject: Re: [mainline][BUG] Observed Workqueue lockups on offline CPUs.
Date: Thu, 30 Apr 2026 21:06:32 +0530	[thread overview]
Message-ID: <4597b29c-3548-482f-9a34-8d69a59d77fd@linux.ibm.com> (raw)
In-Reply-To: <16676927-5a4a-4007-9ece-593a4699adb0@paulmck-laptop>


On 30/04/26 8:30 pm, Paul E. McKenney wrote:
> On Thu, Apr 30, 2026 at 11:49:02AM +0530, Samir M wrote:
>> On 29/04/26 11:21 pm, Shrikanth Hegde wrote:
>>> Hi Samir.
>>>
>>> On 4/29/26 3:46 PM, Samir M wrote:
>>>> Hi Boqun,
>>>>
>>>> Thank you for pointing me to the existing patches. I have tested
>>>> both Paul's patch [1] and TJ's workqueue patch [2] on my PowerPC
>>>> system (80 CPUs), and can confirm that the workqueue lockup issue is
>>>> not observed.
>>>>
>>> Can you try only paul's patch and confirm if the issue is fixed?
>>>
>> Hi Shrikanth,
>>
>> I have verified Paul’s “alone” patch, and it resolves the issue no workqueue
>> lockups are observed.
> Thank you, Samir!  May I add your Tested-by?
>
> 							Thanx, Paul

Hi Paul,

Yes, you may add:
Tested-by: Samir <samir@linux.ibm.com>

Thanks,
Samir
>> Regards,
>> Samir.
>>
>>
>>>> Test Environment:
>>>> - System: PowerPC with 80 CPUs ( e.g. PowerPC LPARs with 80 online
>>>> and 384 possible CPUs)
>>>> - Kernel version: Latest upstream (7.1-rc1)
>>>>
>>>> Regression Testing Results:
>>>> All tests completed successfully with no issues observed:
>>>> - Hackbench
>>>> - Kernel selftests
>>>> - LTP scheduler tests
>>>>
>>>> The workqueue lockup that was previously occurring is no longer
>>>> present with the patches applied.
>>>>
>>>> References:
>>>> [1]: https://lore.kernel.org/rcu/ed1fa6cd-7343-4ca3-8b9d-
>>>> d699ca496f83@paulmck-laptop/
>>>> [2]: https://lore.kernel.org/rcu/adlHKowvhn8AGXCc@slm.duckdns.org/
>>>>
>>>> Best regards,
>>>> Samir

      reply	other threads:[~2026-04-30 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 10:02 [mainline][BUG] Observed Workqueue lockups on offline CPUs Samir M
2026-04-27 11:30 ` Samir M
2026-04-27 15:43   ` Boqun Feng
2026-04-29 10:16     ` Samir M
2026-04-29 17:51       ` Shrikanth Hegde
2026-04-30  6:19         ` Samir M
2026-04-30 15:00           ` Paul E. McKenney
2026-04-30 15:36             ` Samir M [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=4597b29c-3548-482f-9a34-8d69a59d77fd@linux.ibm.com \
    --to=samir@linux.ibm.com \
    --cc=boqun.feng@gmail.com \
    --cc=boqun@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=sshegde@linux.ibm.com \
    --cc=tj@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