public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Brian Bunker <brian@purestorage.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,
	Seamus Connor <sconnor@purestorage.com>,
	Krishna Kant <krishna.kant@purestorage.com>
Subject: Re: [PATCH] scsi: sd: Avoid sending an INQUIRY if the page is not supported
Date: Wed, 10 May 2023 10:29:11 -0400	[thread overview]
Message-ID: <yq1mt2cxo07.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <81D851CF-423E-480C-80C1-F05CB67E5322@purestorage.com> (Brian Bunker's message of "Mon, 8 May 2023 09:04:28 -0700")


Brian,

> Do they report nothing when VPD page 0 is requested or an incomplete
> list that doesn’t include this 0xb9?

Unfortunately both scenarios are relatively common.

>> What exactly is the problem you are experiencing wrt. your target
>> getting an inquiry for the CPR page?
>
> What happens for us is that our support and customers are used to
> looking for errors when they see a problem as you would expect. When
> we are logging VPD page 0xb9 not supported for every device every time
> a Linux host reboots

I suggest you stop logging errors in that case.

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2023-05-10 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 20:49 [PATCH] scsi: sd: Avoid sending an INQUIRY if the page is not supported Brian Bunker
2023-05-08 10:09 ` Benjamin Block
2023-05-08 16:34   ` Brian Bunker
2023-05-11 16:44     ` Benjamin Block
2023-05-12  2:58       ` Douglas Gilbert
2023-05-08 12:26 ` Martin K. Petersen
2023-05-08 16:04   ` Brian Bunker
2023-05-10 14:29     ` Martin K. Petersen [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=yq1mt2cxo07.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=brian@purestorage.com \
    --cc=krishna.kant@purestorage.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sconnor@purestorage.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