Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Amitai Gottlieb <amitaig@hailo.ai>, <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <amitaigottlieb@gmail.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [PATCH] [STABLE ONLY] firmware: arm_scmi: Fix unused notifier-block in unregister
Date: Tue, 16 Dec 2025 09:40:31 +0000	[thread overview]
Message-ID: <20251216-quantum-amazing-giraffe-fd9dfa@sudeepholla> (raw)
In-Reply-To: <20251216090009.13435-1-amitaig@hailo.ai>

Hi Amitai,

Not sure if you received my earlier reply as I can't find it on the list
and not in sent box as well. But I do see you have cc-ed Greg as requested
but didn't consider other requests, hence the confusion.

Hi Greg,

This is first time I am deal with such an issue which exist only in the
stable tree as the upstream fixed it in some refactoring before the issue
was reported/known. Let us know if this is correct way to add patch to
stable tree only or is there something we are missing or need to take care of.

On Tue, Dec 16, 2025 at 11:00:09AM +0200, Amitai Gottlieb wrote:
> In function `scmi_devm_notifier_unregister` the notifier-block parameter
> was unused and therefore never passed to `devres_release`. This causes
> the function to always return -ENOENT and fail to unregister the
> notifier.
> 
> In drivers that rely on this function for cleanup this causes
> unexpected failures including kernel-panic.
> 
> This is not needed upstream becaues the bug was fixed
> in a refactor by commit 264a2c520628 ("firmware: arm_scmi: Simplify
> scmi_devm_notifier_unregister").  


> It is needed for the 5.15, 6.1 and 6.6 kernels.

I had given you reworded commit message and particularly the above text
to be dropped. It makes no sense to add this say is v5.15 kernel e.g.

> 
> Cc: <stable@vger.kernel.org> # 5.15.x, 6.1.x, and 6.6.x
> Fixes: 5ad3d1cf7d34 ("firmware: arm_scmi: Introduce new devres notification ops")
> Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
> Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>

I had also asked you to add my

Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>

-- 
Regards,
Sudeep

      reply	other threads:[~2025-12-16  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  9:00 [PATCH] [STABLE ONLY] firmware: arm_scmi: Fix unused notifier-block in unregister Amitai Gottlieb
2025-12-16  9:40 ` Sudeep Holla [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=20251216-quantum-amazing-giraffe-fd9dfa@sudeepholla \
    --to=sudeep.holla@arm.com \
    --cc=amitaig@hailo.ai \
    --cc=amitaigottlieb@gmail.com \
    --cc=cristian.marussi@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.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