linux-kernel - Re: [PATCH] [SCSI] sd: Lower printk level for drive cache information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 29 Nov 2011 10:03:16 -0500
From:	Josh Boyer <jwboyer@...hat.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"James E.J. Bottomley" <JBottomley@...allels.com>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [SCSI] sd: Lower printk level for drive cache information

On Mon, Nov 28, 2011 at 11:44:42PM -0500, Christoph Hellwig wrote:
> On Mon, Nov 28, 2011 at 11:31:55AM -0500, Josh Boyer wrote:
> > Numerous devices don't present cache data, particularly USB sticks.  The
> > devices operate correctly despite this, so lower the printk severity to
> > KERN_NOTICE.
> 
> Do they?  The last reports on the list were for devices that didn't
> present it but actually needed cache flushes despite not having the
> cache mode page.

We've seen a number of reports for liveusb images that spit out those
printks, but seem to otherwise work fine.

Even if the devices need cache flushes, what is a typical user supposed
to do about that?  I'm not particularly tied to this patch, but there is
nothing a normal user can do with the information spit out by these
printks, so making it KERN_ERR seems excessive.

josh
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/