From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: npiggin@gmail.com, christophe.leroy@csgroup.eu,
Qiheng Lin <linqiheng@huawei.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: Fix potential memleak in papr_get_attr()
Date: Thu, 14 Mar 2024 00:19:43 +1100 [thread overview]
Message-ID: <171033598340.517247.11139891507654380344.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20221208133449.16284-1-linqiheng@huawei.com>
On Thu, 08 Dec 2022 21:34:49 +0800, Qiheng Lin wrote:
> `buf` is allocated in papr_get_attr(), and krealloc() of `buf`
> could fail. We need to free the original `buf` in the case of failure.
>
>
Applied to powerpc/next.
[1/1] powerpc/pseries: Fix potential memleak in papr_get_attr()
https://git.kernel.org/powerpc/c/cda9c0d556283e2d4adaa9960b2dc19b16156bae
cheers
prev parent reply other threads:[~2024-03-13 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 13:34 [PATCH] powerpc/pseries: Fix potential memleak in papr_get_attr() Qiheng Lin
2022-12-08 13:34 ` Qiheng Lin
2024-03-13 13:19 ` Michael Ellerman [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=171033598340.517247.11139891507654380344.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linqiheng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@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.