target-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, Mike Christie <michael.christie@oracle.com>
Subject: Re: [RFC PATCH] scsi: target: detect XCOPY NAA descriptor conflicts
Date: Thu, 13 Aug 2020 11:08:25 +0000	[thread overview]
Message-ID: <20200813130825.67cf86d0@suse.de> (raw)
In-Reply-To: <20200813002142.13820-1-ddiss@suse.de>

FWIW, tcmu-runner appears to use the same vpd_unit_serial -> NAA WWN
mapping logic. I'll provide a patch for it too, once we decide on the
best way to address this issue.

Cheers, David

  reply	other threads:[~2020-08-13 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  0:21 [RFC PATCH] scsi: target: detect XCOPY NAA descriptor conflicts David Disseldorp
2020-08-13 11:08 ` David Disseldorp [this message]
2020-08-24 16:56 ` David Disseldorp
2020-09-02  3:17 ` Michael Christie
2020-09-02 22:23   ` David Disseldorp
2020-09-03 15:36     ` Michael Christie
2020-09-03 20:54       ` David Disseldorp

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=20200813130825.67cf86d0@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michael.christie@oracle.com \
    --cc=target-devel@vger.kernel.org \
    /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).