From: Dan Carpenter <error27@gmail.com>
To: Alexandru Hossu <hossu.alexandru@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] staging: nvec: fix unconditional pm_power_off teardown
Date: Mon, 13 Apr 2026 20:51:33 +0300 [thread overview]
Message-ID: <ad0tJefABBGz0LQc@stanley.mountain> (raw)
In-Reply-To: <20260413151236.612404-1-hossu.alexandru@gmail.com>
On Mon, Apr 13, 2026 at 05:12:36PM +0200, Alexandru Hossu wrote:
> tegra_nvec_remove() unconditionally sets pm_power_off = NULL, even if
> nvec was not the one that registered it. This breaks any other driver
> that may have set pm_power_off to its own handler.
>
> Replace the unconditional assignment with a guarded check so that
> pm_power_off is only cleared if nvec was the one that set it.
>
> Also remove the stale FIXME comment, as the guard addresses exactly
> what it was asking for.
>
> Fixes: 3f8d52ba1c49 ("staging: nvec: Remove nvec_power module")
> Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
> ---
> v2:
> - Drop nvec_power_handle = NULL; after pm_power_off = NULL is set,
> nvec_power_off() is unreachable via pm_power_off, so there is no
> dangling-pointer risk there (Dan Carpenter)
Thanks!
Reviewed-by: Dan Carpenter <error27@gmail.com>
regards,
dan carpenter
next prev parent reply other threads:[~2026-04-14 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 15:12 [PATCH v2 1/2] staging: nvec: fix use-after-free in nvec_rx_completed() Alexandru Hossu
2026-04-13 15:12 ` [PATCH v2 2/2] staging: nvec: fix unconditional pm_power_off teardown Alexandru Hossu
2026-04-13 17:51 ` Dan Carpenter [this message]
2026-04-13 20:02 ` [PATCH v3] " Alexandru Hossu
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=ad0tJefABBGz0LQc@stanley.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hossu.alexandru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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