linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Ajish.Koshy@microchip.com>
To: <john.garry@huawei.com>, <jinpu.wang@ionos.com>,
	<Viswas.G@microchip.com>
Cc: <linux-scsi@vger.kernel.org>, <vishakhavc@google.com>,
	<ipylypiv@google.com>, <Ruksar.devadi@microchip.com>,
	<damien.lemoal@opensource.wdc.com>,
	<Vasanthalakshmi.Tharmarajan@microchip.com>
Subject: RE: [issue report] pm8001 issues (was driver crashes with IOMMU enabled)
Date: Tue, 11 Jan 2022 12:40:14 +0000	[thread overview]
Message-ID: <PH0PR11MB511238B8FF7B44C375DDDFADEC519@PH0PR11MB5112.namprd11.prod.outlook.com> (raw)
In-Reply-To: <34319d65-104d-55a0-175d-96cf3f0aea89@huawei.com>

Hi John,

> >> Once the task is dispatched to HW at ****, it is completed async, i.e.
> >> it may be completed and freed at any point, even before the dispatch
> >> function returns. So it is illegal to touch the task at this point
> >> and the task state must be updated before final dispatch to the HW.
> >> If you enable KASAN you will prob see it yell like I saw.
> >>
> > I too have similar thought here. After dispatch to HW, no point to
> > touch the task state. But since the code is in IO path, may need further
> testing.
> >
> 
> Hi,
> 
> Have you made any progress on the hang which I see on my arm64 system?

Not planned for ARM server.

> 
> I think that you said that you can also see it on an arm64 system - would that
> be with a similar card to mine? I think mine is 8008/9

That was similar card i.e. 8076.

> 
> I have tested some older kernels and v4.11 seems much better.
> 
> Thanks,
> John

Just to get more clarification, in the same thread 
following issues were mentioned. Right now
I am on x86 server. Don't have 8008/8009 controller
with me here. 
Issues:
1. Driver crashes when IOMMU is enabled. Patch already
submitted.
   - Issue was seen on x86 server too.
2. Observed triggering of scsi error handler on
   ARM server.
   - Issue not observed on x86 server
3. maxcpus=1 on commandline crashes during bootup. 
   Issue with 8008/8009 controller. Patch created.
   - Issue impacts x86 too based on the code.
4. "I have found another issue. There is a potential
   use-after-free in pm8001_task_exec():", where we
   modify task state post task dispatch to hardware
   - Generic code. Impact on all platform x86 and ARM.
   
Let us know if any other issue missed out to
mention here or issues that impacts x86 too.

Thanks,
Ajish

  reply	other threads:[~2022-01-11 12:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 12:28 [issue report] pm8001 driver crashes with IOMMU enabled John Garry
2021-11-24 12:43 ` Jinpu Wang
2021-11-24 16:22   ` John Garry
2021-12-24  9:02     ` [issue report] pm8001 issues (was driver crashes with IOMMU enabled) John Garry
2021-12-24 11:58       ` John Garry
2021-12-27 13:26         ` Ajish.Koshy
2022-01-06 15:49           ` John Garry
2022-01-07 11:12             ` Ajish.Koshy
2022-01-10 20:21               ` John Garry
2022-01-11 12:40                 ` Ajish.Koshy [this message]
2022-01-11 13:23                   ` John Garry
2022-01-13 12:52                     ` Ajish.Koshy
2022-01-13 14:17                       ` John Garry
2022-01-14 18:21                         ` John Garry
2022-01-17 13:56                           ` Ajish.Koshy
2022-01-17 14:02                         ` Ajish.Koshy
2022-01-18 15:49                           ` John Garry
2022-01-19 13:49                             ` Ajish.Koshy

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=PH0PR11MB511238B8FF7B44C375DDDFADEC519@PH0PR11MB5112.namprd11.prod.outlook.com \
    --to=ajish.koshy@microchip.com \
    --cc=Ruksar.devadi@microchip.com \
    --cc=Vasanthalakshmi.Tharmarajan@microchip.com \
    --cc=Viswas.G@microchip.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=ipylypiv@google.com \
    --cc=jinpu.wang@ionos.com \
    --cc=john.garry@huawei.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vishakhavc@google.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).