Linux CXL
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: KASAN error when insmod cxl_test
Date: Tue, 15 Oct 2024 09:34:57 -0500	[thread overview]
Message-ID: <670e7d9125fc0_156512294db@iweiny-mobl.notmuch> (raw)
In-Reply-To: <670de32847e6d_3f1429473@dwillia2-xfh.jf.intel.com.notmuch>

Dan Williams wrote:
> Huang, Ying wrote:
> > Hi, Dave,
> > 
> > When I tried to test v6.12-rc2 with cxl_test in qemu, the below error is
> > reported.  Revert commit a5ab0de0ebaa ("cxl: Calculate region bandwidth
> > of targets with shared upstream link") can eliminate the error.
> > 
> > Can you take a look at it?
> 
> Does the same reproduce with "modprobe cxl_test"? I worry that direct
> 'insmod' usage results in cases where it proceeds with the wrong
> dependencies. I.e. I never test with insmod, only modprobe, and my
> v6.12-rc2 testing so far has not hit this.
> 

For me this is only happening when I boot qemu.  I don't see this error
when I use modprobe or insmod after boot.

It only happens when I use cxl_test and not qemu test devices.  Which
means Zhijian is probably the best solution.  I'm testing his mock diff
now.

Ira

  parent reply	other threads:[~2024-10-15 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  9:03 KASAN error when insmod cxl_test Huang, Ying
2024-10-15  2:41 ` Ira Weiny
2024-10-15  3:36 ` Dan Williams
2024-10-15  4:56   ` Huang, Ying
2024-10-15 14:34   ` Ira Weiny [this message]
2024-10-15  8:39 ` Zhijian Li (Fujitsu)
2024-10-15  9:41   ` Zhijian Li (Fujitsu)
2024-10-15 15:53     ` Ira Weiny
2024-10-15 18:06     ` Dan Williams
2024-10-16  1:23       ` Zhijian Li (Fujitsu)

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=670e7d9125fc0_156512294db@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=ying.huang@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