From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
Long Li <longli@microsoft.com>, Dexuan Cui <decui@microsoft.com>
Subject: Re: [PATCH v2] scsi: introduce short_inquiry flag for broken host adapters
Date: Tue, 15 Sep 2015 11:24:05 -0700 [thread overview]
Message-ID: <1442341445.2177.9.camel@HansenPartnership.com> (raw)
In-Reply-To: <87k2rryczs.fsf@vitty.brq.redhat.com>
On Tue, 2015-09-15 at 16:27 +0200, Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov <vkuznets@redhat.com> writes:
>
> > Some host adapters (e.g. Hyper-V storvsc) are known for not respecting the
> > SPC-2/3/4 requirement for 'INQUIRY data (see table ...) shall contain at
> > least 36 bytes'. As a result we get tons on 'scsi 0:7:1:1: scsi scan:
> > INQUIRY result too short (5), using 36' messages on console. This can be
> > problematic for slow consoles. Introduce short_inquiry host template flag
> > to avoid printing error messages for such adapters.
> >
> > Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> > ---
> > Changes since v1:
> > - This is a successor of previously sent "scsi_scan: move 'INQUIRY result
> > too short' message to debug level" patch. Instead of moving the message
> > to debug level for all adapters introduce a special 'short_inquiry' flag
> > for host template [inspired by James Bottomley].
>
> James,
>
> sorry for the ping but can you please let me know your opinion? This is
> not a 'cosmetic fix', serial port on Hyper-V is extremely slow and users
> get softlockups just because we output too much. Here is a freshly
> booted guest with SCSI and FC adapters connected:
>
> # dmesg | grep -c INQUIRY
> 2076
It needs a review ... preferably from someone who validates that we
don't get any adverse impact from the missing inquiry data
> (my other pernding '[PATCH] scsi_scan: don't dump trace when
> scsi_prep_async_scan() is called twice' is related to the same issue).
So does this.
James
> See also: https://lkml.org/lkml/2015/9/6/119
>
> Thanks,
>
> [...]
>
next prev parent reply other threads:[~2015-09-15 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 16:11 [PATCH v2] scsi: introduce short_inquiry flag for broken host adapters Vitaly Kuznetsov
2015-09-15 14:27 ` Vitaly Kuznetsov
2015-09-15 18:24 ` James Bottomley [this message]
2015-09-15 19:55 ` KY Srinivasan
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=1442341445.2177.9.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=decui@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=vkuznets@redhat.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