From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christian Loehle <cloehle@hyperstone.com>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: sd_spinup_disk() now is a little noisy
Date: Sat, 11 Sep 2021 00:59:26 +0200 [thread overview]
Message-ID: <485ac2f7-e83a-6fcd-b849-c20608e26810@gmail.com> (raw)
For my personal taste sd_spinup_disk() is a little bit noisy now.
[ 1.942179] scsi 0:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0
[ 1.943651] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.943667] sd 0:0:0:0: [sda] Media removed, stopped polling
[ 1.949970] sd 0:0:0:0: [sda] Media removed, stopped polling
[ 1.950001] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 1.959266] sd 0:0:0:0: [sda] Media removed, stopped polling
There's not really a benefit in printing the same message multiple
times. The following helped for me, not sure however whether
that's the right way to deal with it.
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index cbd9999f9..af7e7b0da 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2124,6 +2124,8 @@ sd_spinup_disk(struct scsi_disk *sdkp)
retries = 0;
do {
+ u8 media_was_present = sdkp->media_present;
+
cmd[0] = TEST_UNIT_READY;
memset((void *) &cmd[1], 0, 9);
@@ -2138,7 +2140,8 @@ sd_spinup_disk(struct scsi_disk *sdkp)
* with any more polling.
*/
if (media_not_present(sdkp, &sshdr)) {
- sd_printk(KERN_NOTICE, sdkp, "Media removed, stopped polling\n");
+ if (media_was_present)
+ sd_printk(KERN_NOTICE, sdkp, "Media removed, stopped polling\n");
return;
}
--
2.33.0
next reply other threads:[~2021-09-10 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 22:59 Heiner Kallweit [this message]
2021-09-11 2:37 ` sd_spinup_disk() now is a little noisy Bart Van Assche
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=485ac2f7-e83a-6fcd-b849-c20608e26810@gmail.com \
--to=hkallweit1@gmail.com \
--cc=cloehle@hyperstone.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