qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Cc: Zhao Liu <zhao1.liu@linux.intel.com>, Fan Ni <fan.ni@samsung.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>,
	Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [PATCH] hw/cxl/cxl-host: Fix guest crash when getting cxl-fmw property
Date: Fri, 5 Jul 2024 12:40:38 +0100	[thread overview]
Message-ID: <20240705124038.0000053c@huawei.com> (raw)
In-Reply-To: <3cccc5ba-81b9-4391-b187-27562ebc6c85@fujitsu.com>

On Fri, 5 Jul 2024 02:39:51 +0000
"Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com> wrote:

> On 04/07/2024 17:34, Zhao Liu wrote:
> > From: Zhao Liu <zhao1.liu@intel.com>
> > 
> > Guest crashes (Segmentation fault) when getting cxl-fmw property via
> > qmp:
> >   
> 
> IMO, it's fair to say "Guest crashes" which generally means the guest kernel panic etc.
> I'd prefer the subject like:
> hw/cxl/cxl-host: Fix segmentation fault when getting cxl-fmw property
Agreed. I've picked this up and edited the description.

I've just hit send on a v2 of the misc minor fixes series with this
replacing the patch that dropped cfmws_list

Thanks,

Jonathan


> 
> 
> Otherwise,
> 
> Reviewed-by: Li Zhijian <lizhijian@fujitsu.com>
> 
> 
> > (QEMU) qom-get path=machine property=cxl-fmw
> > 
> > This issue is caused by accessing wrong callback (opaque) type in
> > machine_get_cfmw().
> > 
> > cxl_machine_init() sets the callback as `CXLState *` type but
> > machine_get_cfmw() treats the callback as
> > `CXLFixedMemoryWindowOptionsList **`.
> > 
> > Fix this error by casting opaque to `CXLState *` type in
> > machine_get_cfmw().
> > 
> > Fixes: 03b39fcf64bc ("hw/cxl: Make the CXL fixed memory window setup a machine parameter.")
> > Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> > ---
> >   hw/cxl/cxl-host.c | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/hw/cxl/cxl-host.c b/hw/cxl/cxl-host.c
> > index c5f5fcfd64d0..e9f2543c43c6 100644
> > --- a/hw/cxl/cxl-host.c
> > +++ b/hw/cxl/cxl-host.c
> > @@ -315,7 +315,8 @@ static void machine_set_cxl(Object *obj, Visitor *v, const char *name,
> >   static void machine_get_cfmw(Object *obj, Visitor *v, const char *name,
> >                                void *opaque, Error **errp)
> >   {
> > -    CXLFixedMemoryWindowOptionsList **list = opaque;
> > +    CXLState *state = opaque;
> > +    CXLFixedMemoryWindowOptionsList **list = &state->cfmw_list;
> >   
> >       visit_type_CXLFixedMemoryWindowOptionsList(v, name, list, errp);
> >     



      reply	other threads:[~2024-07-05 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  9:34 [PATCH] hw/cxl/cxl-host: Fix guest crash when getting cxl-fmw property Zhao Liu
2024-07-05  0:53 ` Xingtao Yao (Fujitsu) via
2024-07-05  2:39 ` Zhijian Li (Fujitsu) via
2024-07-05 11:40   ` 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=20240705124038.0000053c@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=fan.ni@samsung.com \
    --cc=lizhijian@fujitsu.com \
    --cc=qemu-stable@nongnu.org \
    --cc=zhao1.liu@intel.com \
    --cc=zhao1.liu@linux.intel.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;
as well as URLs for NNTP newsgroup(s).