From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Fan Ni" <fan.ni@samsung.com>,
linuxarm@huawei.com, "Zeng Hao" <zenghao@kylinos.cn>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 0/2] hw/cxl: CDAT file handling fixes.
Date: Mon, 22 May 2023 12:06:01 +0100 [thread overview]
Message-ID: <20230522120601.000029cc@Huawei.com> (raw)
In-Reply-To: <d53a8882-eb59-cf09-6ab7-b4a712f20668@tls.msk.ru>
On Sat, 20 May 2023 07:46:16 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> 21.04.2023 16:20, Jonathan Cameron via wrote:
> > I've picked up Hao Zeng's v5 and added a patch to deal with the
> > issues that Peter pointed out in this area.
> >
> > On error, the CDAT file handling left resource dangling and didn't
> > cleanly exit from calling functions. Hao Zeng dealt with closing
> > the file. The second patch deals with the buffer allocation and
> > ensuring a clean exit at the two callers.
> >
> > Hao Zeng (1):
> > hw/cxl: cdat: Fix open file not closed in ct3_load_cdat()
> >
> > Jonathan Cameron (1):
> > hw/cxl: cdat: Fix failure to free buffer in erorr paths
> >
> > hw/cxl/cxl-cdat.c | 60 +++++++++++++++---------------------
> > hw/mem/cxl_type3.c | 4 +++
> > hw/pci-bridge/cxl_upstream.c | 3 ++
> > 3 files changed, 32 insertions(+), 35 deletions(-)
>
> Hi!
>
> Is it a stable (8.0 & 7.2) material?
> The issues does not seem to be very important, still smells like
> a good thing to have in -stable.
Issues are leaks only on an error path, so I'd say no for stable.
If others disagree these should be harmless.
Jonathan
>
> Thanks,
>
> /mjt
>
prev parent reply other threads:[~2023-05-22 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 13:20 [PATCH 0/2] hw/cxl: CDAT file handling fixes Jonathan Cameron via
2023-04-21 13:20 ` [PATCH 1/2] hw/cxl: cdat: Fix open file not closed in ct3_load_cdat() Jonathan Cameron via
[not found] ` <CGME20230516161447uscas1p2655c105517bf73bdfc55bb972ed3693f@uscas1p2.samsung.com>
2023-05-16 16:14 ` Fan Ni
2023-04-21 13:20 ` [PATCH 2/2] hw/cxl: cdat: Fix failure to free buffer in erorr paths Jonathan Cameron via
[not found] ` <CGME20230516161524uscas1p1bba689b7fe90149e8d899b249d04bea0@uscas1p1.samsung.com>
2023-05-16 16:15 ` Fan Ni
2023-05-20 4:46 ` [PATCH 0/2] hw/cxl: CDAT file handling fixes Michael Tokarev
2023-05-22 11:06 ` Jonathan Cameron via [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=20230522120601.000029cc@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=fan.ni@samsung.com \
--cc=linuxarm@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=zenghao@kylinos.cn \
/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;
as well as URLs for NNTP newsgroup(s).