public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@hpe.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
	Yi Zhang <yi.zhang@redhat.com>,
	Baolu Lu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	linux-block <linux-block@vger.kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>
Subject: Re: [bug report][regression] blktests block/008 lead kerne panic at RIP: 0010:amd_iommu_enable_faulting+0x0/0x10
Date: Wed, 29 May 2024 07:49:34 -0500	[thread overview]
Message-ID: <ZlckXh4rZ+sWRqXR@hpe.com> (raw)
In-Reply-To: <BN9PR11MB5276CBD826F1E95D28B2E30A8CF22@BN9PR11MB5276.namprd11.prod.outlook.com>

On Wed, May 29, 2024 at 08:13:42AM +0000, Tian, Kevin wrote:
> > From: Vasant Hegde <vasant.hegde@amd.com>
> > Sent: Wednesday, May 29, 2024 2:26 PM
> > 
> > Hi Yi,
> > 
> > +Dimitri, Lu, Tian.
> > 
> > 
> > On 5/29/2024 11:46 AM, Yi Zhang wrote:
> > > On Wed, May 29, 2024 at 1:40 AM Vasant Hegde <vasant.hegde@amd.com>
> > wrote:
> > >>
> > >> Hi Yi,
> > >>
> > >>
> > >> On 5/28/2024 11:00 PM, Vasant Hegde wrote:
> > >>> Hi Yi,
> > >>>
> > >>>
> > >>> On 5/28/2024 10:30 AM, Joerg Roedel wrote:
> > >>>> Adding Vasant.
> > >>>>
> > >>>> On Tue, May 28, 2024 at 10:23:10AM +0800, Yi Zhang wrote:
> > >>>>> Hello
> > >>>>> I found this regression panic issue on the latest 6.10-rc1 and it
> > >>>>> cannot be reproduced on 6.9, please help check and let me know if
> > you
> > >>>>> need any info/testing for it, thanks.
> > >>>
> > >>> I have tried to reproduce this issue on my system. So far I am not able to
> > >>> reproduce it.
> > >>>
> > >>> Will you be able to bisect the kernel?
> > >>
> > >> I see that below patch touched this code path. Can you revert below patch
> > and
> > >> test it again?
> > >
> > > Yes, the panic cannot be reproduced now after revert this patch.
> > 
> > Thanks for verifying. AMD code path (amd_iommu_enable_faulting()) just
> > return
> > zero. It doesn't do anything else. I am not familiar with cpuhp_setup_state()
> > code path.
> > 
> > @Dimitri, Can you look into this issue?
> > 
> 
> -int __init amd_iommu_enable_faulting(void)
> +int __init amd_iommu_enable_faulting(unsigned int cpu)
> 
> likely it's due to '__init' not being removed...

Yes, agreed.  I will submit a patch with this change soon.


      reply	other threads:[~2024-05-29 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  2:23 [bug report][regression] blktests block/008 lead kerne panic at RIP: 0010:amd_iommu_enable_faulting+0x0/0x10 Yi Zhang
2024-05-28  5:00 ` Joerg Roedel
2024-05-28 17:30   ` Vasant Hegde
2024-05-28 17:40     ` Vasant Hegde
2024-05-29  6:16       ` Yi Zhang
2024-05-29  6:26         ` Vasant Hegde
2024-05-29  8:13           ` Tian, Kevin
2024-05-29 12:49             ` Dimitri Sivanich [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=ZlckXh4rZ+sWRqXR@hpe.com \
    --to=sivanich@hpe.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=yi.zhang@redhat.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