Re: qla2xxx Call Trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 31, 2014 at 5:22 PM, Nicholas A. Bellinger
<nab@xxxxxxxxxxxxxxx> wrote:
> Roland + Joern, I'm specifically talking about the following patches:
>
> https://github.com/rolandd/qla-target/commit/77bd729e5e9f858495dfded7c08e548bc9ecc9be
> https://github.com/rolandd/qla-target/commit/79ae07a141950c0008480a46f91d72318a1d799e
>
> Can you please confirm if these are related to what deeepdish has
> reported here..?

Our latest tree doesn't use the btree -> radix tree conversion -- we
decided there is nothing wrong with the btree code itself.  So from
that POV upstream is fine.

However the first (77bd...) commit may be related.  Certainly the
comment is true: the qla2xxx target stuff is racy, especially around
fabric changes (initiators/sessions coming and going).  It looks like
the original trace has to do with session update, so yeah, it probably
is hitting one of those races.

 - R.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux