From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Haren Myneni <haren@linux.ibm.com>,
Tyrel Datwyler <tyreld@linux.ibm.com>,
Christian Brauner <brauner@kernel.org>,
Kees Cook <kees@kernel.org>,
Guangshuo Li <lgs201920130244@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/pseries/papr-hvpipe: fix NULL dereference in handle creation
Date: Tue, 21 Apr 2026 06:34:37 +0530 [thread overview]
Message-ID: <fr4pt97e.ritesh.list@gmail.com> (raw)
In-Reply-To: <20260420132429.128075-1-lgs201920130244@gmail.com>
Guangshuo Li <lgs201920130244@gmail.com> writes:
> papr_hvpipe_dev_create_handle() transfers ownership of src_info with
> retain_and_null_ptr(src_info) after anon_inode_getfile() succeeds.
> However, retain_and_null_ptr() clears src_info immediately, and the
> function then still dereferences src_info in the subsequent list_add().
>
> Store the transferred pointer in a separate variable and use that for
> the list insertion.
>
> Manually identified during code review.
Thanks. Although the fix for this and bunch of other fixes & cleanups
were already queued up for review in here [1].
[1]: https://lore.kernel.org/all/cover.1775648406.git.ritesh.list@gmail.com/
-ritesh
prev parent reply other threads:[~2026-04-21 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 13:24 [PATCH v2] powerpc/pseries/papr-hvpipe: fix NULL dereference in handle creation Guangshuo Li
2026-04-21 1:04 ` Ritesh Harjani [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=fr4pt97e.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=brauner@kernel.org \
--cc=chleroy@kernel.org \
--cc=haren@linux.ibm.com \
--cc=kees@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tyreld@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