linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Smart <james.smart@broadcom.com>
Cc: Dick Kennedy <dick.kennedy@broadcom.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] lpfc: nodelist pointer cleanup
Date: Sat, 19 Oct 2019 17:55:58 +0200	[thread overview]
Message-ID: <6decf1ca-0cbb-3d86-8500-78ae36c69012@suse.de> (raw)
In-Reply-To: <ced4e239-40b2-508a-f52a-1b7baf674f04@broadcom.com>

On 10/18/19 11:45 PM, James Smart wrote:
> On 10/18/2019 12:50 AM, Hannes Reinecke wrote:
>> Hi James,
>>
>> trying to figure this annoying lpfc_set_rrq_active() bug
>> I've found the nodelist pointer handling in the lpfc io buffers
>> a bit strange; there's a 'ndlp' pointer, but for scsi the nodelist
>> is primarily accessed via the 'rdata' pointer (although not everywhere).
>> For NVMe it's primarily the 'ndlp' pointer, apparently, but the
>> usage is quite confusing.
>> So here's a patchset to straighten things up; it primarily moves
>> the anonymous protocol-specific structure in the io buffer to a named
>> one, and always accesses the nodelist through the protocol-specific
>> rport data structure.
>>
>> It also has the nice side-effect that the protocol-specific areas are
>> aligned now, so clearing the 'rdata' pointer on the scsi side will
>> be equivalent to clearing the 'rport' pointer on the nvme side.
>> And it reduces the size of the io buffer.
>>
>> Let me know what you think.
>>
>> Hannes Reinecke (3):
>>    lpfc: use named structure for combined I/O buffer
>>    lpfc: access nodelist through scsi-specific rdata pointer
>>    lpfc: access nvme nodelist through nvme rport structure
>>
>>   drivers/scsi/lpfc/lpfc_init.c |   2 +-
>>   drivers/scsi/lpfc/lpfc_nvme.c |  56 ++++++------
>>   drivers/scsi/lpfc/lpfc_scsi.c | 196 
>> +++++++++++++++++++++---------------------
>>   drivers/scsi/lpfc/lpfc_sli.c  |  26 +++---
>>   drivers/scsi/lpfc/lpfc_sli.h  |   6 +-
>>   5 files changed, 143 insertions(+), 143 deletions(-)
>>
> 
> Well, the problem I think you are trying to solve is ultimately the root 
> issue that is solved by this patch in the just-posted 12.6.0.0 patch set:
> [PATCH 05/16] lpfc: Fix bad ndlp ptr in xri aborted handling
> 
> As such, I'd like to see if the 12.6.0.0 patch resolves the issue before 
> going through all the shifting in your patches.
> Note: the failing routine can change as it's totally dependent on where 
> the bogus pointer value takes you.  The key is the 
> lpfc_sli4_sp_handle_abort_xri_wcqe() routine on the stack.
> 
Fair enough.

I'll be giving your patchset a spin once submitted.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke            Teamlead Storage & Networking
hare@suse.de                              +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)

      reply	other threads:[~2019-10-19 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:50 [RFC PATCH 0/3] lpfc: nodelist pointer cleanup Hannes Reinecke
2019-10-18  7:50 ` [PATCH 1/3] lpfc: use named structure for combined I/O buffer Hannes Reinecke
2019-10-18  7:50 ` [PATCH 2/3] lpfc: access nodelist through scsi-specific rdata pointer Hannes Reinecke
2019-10-18  7:50 ` [PATCH 3/3] lpfc: access nvme nodelist through nvme rport structure Hannes Reinecke
2019-10-18 21:45 ` [RFC PATCH 0/3] lpfc: nodelist pointer cleanup James Smart
2019-10-19 15:55   ` Hannes Reinecke [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=6decf1ca-0cbb-3d86-8500-78ae36c69012@suse.de \
    --to=hare@suse.de \
    --cc=dick.kennedy@broadcom.com \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=james.smart@broadcom.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).