All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: jianqi.ren.cn@windriver.com
Cc: abelova@astralinux.ru, stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y] cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value
Date: Fri, 6 Dec 2024 11:05:45 +0100	[thread overview]
Message-ID: <2024120619-dolphin-outlying-c78d@gregkh> (raw)
In-Reply-To: <20241206104115.1273254-1-jianqi.ren.cn@windriver.com>

On Fri, Dec 06, 2024 at 06:41:15PM +0800, jianqi.ren.cn@windriver.com wrote:
> From: Anastasia Belova <abelova@astralinux.ru>
> 
> [ Upstream commit 5493f9714e4cdaf0ee7cec15899a231400cb1a9f ]
> 
> cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it
> and return in case of error.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Signed-off-by: Anastasia Belova <abelova@astralinux.ru>
> Reviewed-by: Perry Yuan <perry.yuan@amd.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Jianqi Ren <jianqi.ren.cn@windriver.com>
> ---
>  drivers/cpufreq/amd-pstate.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)

Any reason you are not cc:ing all of the people involved in these
patches when backporting them?

thanks,

greg k-h

  reply	other threads:[~2024-12-06 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 10:41 [PATCH 6.1.y] cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value jianqi.ren.cn
2024-12-06 10:05 ` Greg KH [this message]
2024-12-06 17:11 ` Sasha Levin
2024-12-11  8:14 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-12-09  4:19 jianqi.ren.cn
2024-12-09 10:07 ` Anastasia Belova
2024-12-09 14:35 ` Sasha Levin
2024-12-11  9:53 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-11 10:15 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin

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=2024120619-dolphin-outlying-c78d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=abelova@astralinux.ru \
    --cc=jianqi.ren.cn@windriver.com \
    --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 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.