linux-kernel - [PATCH] isci: Make warning messages unique

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-next>] [day] [month] [year] [list]

Message-ID: <4E6E6F94.4050502@canonical.com>
Date:	Mon, 12 Sep 2011 14:46:12 -0600
From:	Tim Gardner <tim.gardner@...onical.com>
To:	dan.j.williams@...el.com, edmund.nadolski@...el.com,
	dave.jiang@...el.com
CC:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: [PATCH] isci: Make warning messages unique

Hi,

I've got a 2-way Sandybridge server with an 'Intel(R) C600 SAS 
Controller'. The driver makes a boatload of dmesg noise with non-unique 
messages distinguished only by the event code. For example, I've got 296 
of these in dmesg:

(NULL device *): sci_phy_event_handler:735: PHY starting substate 
machine received unexpected event_code b3402000

In an effort to discover which of the 9 places from which this message 
was emitted I added a line number.

The next step is to decide if all of these really need to be dev_warn().

rtg
-- 
Tim Gardner tim.gardner@...onical.com

View attachment "0001-isci-Make-warning-messages-unique.patch" of type "text/x-patch" (4792 bytes)