From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
sourabhjain@linux.ibm.com, rppt@kernel.org, baoquan.he@linux.dev,
hbathini@linux.ibm.com, adityag@linux.ibm.com,
ritesh.list@gmail.com, bauerman@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Jinjie Ruan <ruanjinjie@huawei.com>
Subject: Re: [PATCH v2 0/3] powerpc/kexec_file: Fix some bugs
Date: Mon, 3 Aug 2026 12:27:25 +0530 [thread overview]
Message-ID: <178574013469.29744.18290968780763736823.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260729012948.2797865-1-ruanjinjie@huawei.com>
On Wed, 29 Jul 2026 09:29:45 +0800, Jinjie Ruan wrote:
> Fix some powerpc bugs pointed out by Sashiko AI:
> - Memory leak
> - Null-ptr-def
> - Overlapping memory range truncation .
>
> Link: https://lore.kernel.org/all/20260601094805.2928614-1-ruanjinjie@huawei.com/
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/crash: Fix possible memory leak in update_crash_elfcorehdr()
https://git.kernel.org/powerpc/c/4cc4b586007fbbf8edba4f1d0849e9a06b0cf6c3
[2/3] powerpc/kexec_file: Fix null-ptr-def in extra size calculation
https://git.kernel.org/powerpc/c/761eda315a6e1fda3e8e2185b28430771fb1ac29
[3/3] powerpc/kexec_file: Prevent kexec range truncation
https://git.kernel.org/powerpc/c/fa40f9dbdd4af53e7445d9135b5b207eb8adf372
cheers
prev parent reply other threads:[~2026-08-03 6:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 1:29 [PATCH v2 0/3] powerpc/kexec_file: Fix some bugs Jinjie Ruan
2026-07-29 1:29 ` [PATCH v2 1/3] powerpc/crash: Fix possible memory leak in update_crash_elfcorehdr() Jinjie Ruan
2026-07-29 1:29 ` [PATCH v2 2/3] powerpc/kexec_file: Fix null-ptr-def in extra size calculation Jinjie Ruan
2026-07-29 4:01 ` Sourabh Jain
2026-07-29 1:29 ` [PATCH v2 3/3] powerpc/kexec_file: Prevent kexec range truncation Jinjie Ruan
2026-07-29 4:43 ` Sourabh Jain
2026-07-29 6:26 ` Jinjie Ruan
2026-07-29 6:44 ` Sourabh Jain
2026-07-29 7:06 ` Jinjie Ruan
2026-07-29 8:18 ` Sourabh Jain
2026-08-03 6:57 ` Madhavan Srinivasan [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=178574013469.29744.18290968780763736823.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=baoquan.he@linux.dev \
--cc=bauerman@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=sourabhjain@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox