From: Douglas Gilbert <dougg@torque.net>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-2.4.3] scsi logging
Date: Tue, 10 Jul 2001 00:34:05 -0400 [thread overview]
Message-ID: <3B4A85BD.FE0E2D61@torque.net> (raw)
Andrew wrote:
> I'd like to propose the following patch to 3 SCSI mid-layer
> files from kernel 2.4.3. I have tested this with 2.4.3,
> but it should be relevant to other 2.4.x kernels also.
>
> It has the following changes/enhancements:
> 1) Log the disk serial number during scsi_scan()
> - scsi_scan.c.
> Why: This is a requirement in some environments to
> ensure unambiguous identification of a particular
> problem disk.
> 2) Interpret additional values in print_sense_internal()
> - constants.c. Why: The detail wrt Illegal Requests
> is very useful, since it can indicate either an
> application bug or an incompatible feature of the device.
> 3) Don't skip logging sense errors for sg functions - sg.c.
> Why: All sense errors should be logged so that a
> potential scsi device hardware problem doesn't go
> unrecognized.
Andrew,
I would object to point 3). SANE, and to a lesser extent
cdrecord, execute lots of commands that give SCSI check
conditions and would bloat the log and the console with
many serious looking messages. Those error
indications are conveyed back to the app via the sg
interface so the information is not lost. There is an
ioctl in the sg driver [SG_SET_DEBUG] to turn on that
output to the log/console [the default is off (to
stop the curious querying the maintainer about the
strange messages in their logs)].
Doug Gilbert
next reply other threads:[~2001-07-10 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 4:34 Douglas Gilbert [this message]
2001-07-10 13:35 ` [PATCH-2.4.3] scsi logging Eddie Williams
2001-07-10 16:17 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2001-07-10 12:40 Cress, Andrew R
2001-07-09 18:24 Cress, Andrew R
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=3B4A85BD.FE0E2D61@torque.net \
--to=dougg@torque.net \
--cc=andrew.r.cress@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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