All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Joshua Lant <joshualant@googlemail.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: [QEMU- PATCH 1/1] cxl_type3: fix segfault in cxl_destroy_dc_regions
Date: Tue, 9 Sep 2025 15:08:59 +0100	[thread overview]
Message-ID: <20250909150859.000055f3@huawei.com> (raw)
In-Reply-To: <aL754ZJlIUCOCotE@thinkpc>

On Mon, 8 Sep 2025 16:44:33 +0100
Joshua Lant <joshualant@googlemail.com> wrote:

> > On Thu,  4 Sep 2025 10:02:22 +0100
> > Joshua Lant <joshualant@googlemail.com> wrote:
> >   
> > > CXL_TYPE3_CLASS() should be CXL_TYPE3_GET_CLASS() given object (CXLType3Dev)
> > > input. Leads to segfault in object_class_dynamic_cast.
> > > 
> > > Fixes: ef730035567
> > > 
> > > signed-off-by: Joshua Lant <joshualant@gmail.com>  
> > 
> > Good find.
> > 
> > The Fixes tag needs fixing though.
> > Should be all part of the tags block and needs to include the patch name.
> > I'm not finding the SHA though.
> > 
> > I think that tag is probably Svetley's MHD callback patch which isn't upstream
> > so I'll squash this in my local tree and it will be fixed in the next tree
> > I put up on gitlab.com/jic23/
> > 
> > Thanks,
> > 
> > Jonathan  
> 
> Yeah sorry, it is that MHD patch. I managed to write a rogue '7' at the end of
> the hash somehow. Have reposted with updated tags block...
> 
I smashed it into the mhd patch locally and it will end up in there when I push
a new tree, so the fix won't be directly visible as a separate patch.

Thanks anyway for working out what was wrong with the tag.

Jonathan

> Cheers,
> 
> Josh


      reply	other threads:[~2025-09-09 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04  9:02 [QEMU- PATCH 0/1] cxl_type3: segfault in cxl_destroy_dc_regions Joshua Lant
2025-09-04  9:02 ` [QEMU- PATCH 1/1] cxl_type3: fix " Joshua Lant
2025-09-05 14:54   ` Jonathan Cameron
2025-09-08 15:44     ` Joshua Lant
2025-09-09 14:08       ` Jonathan Cameron [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=20250909150859.000055f3@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=joshualant@googlemail.com \
    --cc=linux-cxl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.