From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Yaxing Guo <guoyaxing@bosc.ac.cn>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory
Date: Thu, 26 Feb 2026 06:32:22 -0800 [thread overview]
Message-ID: <2026022659-carry-raisin-05ff@gregkh> (raw)
In-Reply-To: <CANUHTR8hzrnM6s_ysGea3kO8crbeq_onzgcfDTV6UAMB9QFogA@mail.gmail.com>
On Thu, Feb 26, 2026 at 06:14:54PM +0800, Guangshuo Li wrote:
> Hi Greg,
>
> Thanks for the reminder.
>
> This was found by a static analysis tool I designed. After a manual
> review, I confirmed the issue and sent the fix.
>
> Would you prefer that I include the “how it was found and tested”
> information in the commit message?
As per our documentation (please go read it again), it is required :)
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-26 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 1:16 [PATCH v3] uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory Guangshuo Li
2026-02-26 1:38 ` Greg Kroah-Hartman
2026-02-26 10:14 ` Guangshuo Li
2026-02-26 14:32 ` Greg Kroah-Hartman [this message]
2026-02-26 14:45 ` 郭亚星
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=2026022659-carry-raisin-05ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=guoyaxing@bosc.ac.cn \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox