All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: Christophe Leroy <chleroy@kernel.org>,
	Kajol Jain <kjain@linux.ibm.com>,
	linux-kernel@vger.kernel.org,
	Aboorva Devarajan <aboorvad@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/hv-gpci: fix preempt count leak in sysfs show paths
Date: Thu, 14 May 2026 10:54:07 +0530	[thread overview]
Message-ID: <60e44383-0791-4d0a-8c16-41fb4f436e0b@linux.ibm.com> (raw)
In-Reply-To: <5x4usp43.ritesh.list@gmail.com>

Hi Ritesh.

> I guess, these would be the other kind of issues which might show up now,
> since powerpc is moved to CONFIG_PREEMPTION=y with lazy preempt as the
> default preemption mode. It will be nice to have some mechanism to catch
> these error handling paths where preempt counts might be getting leaked.
> 

There is CONFIG_DEBUG_PREEMPT=y which helps you to catch these issue
where count leak happens. Otherwise we only see end result, but not the culprit.


That said, we do have issues of not nesting with get_cpu/put_cpu in few places and
preempt_disable/preempt_enable in few return paths still.


  reply	other threads:[~2026-05-14  5:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  4:12 [PATCH] powerpc/hv-gpci: fix preempt count leak in sysfs show paths Aboorva Devarajan
2026-05-11  1:37 ` Ritesh Harjani
2026-05-14  5:24   ` Shrikanth Hegde [this message]
2026-05-14  5:20 ` Shrikanth Hegde

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=60e44383-0791-4d0a-8c16-41fb4f436e0b@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=aboorvad@linux.ibm.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=ritesh.list@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.