linux-kernel - Re: [PATCH 2/6] mpt3sas: Handle active cable exception event

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

Message-ID: <57333AE3.3090205@redhat.com>
Date:	Wed, 11 May 2016 16:00:03 +0200
From:	Tomas Henzl <thenzl@...hat.com>
To:	Chaitra P B <chaitra.basappa@...adcom.com>, jejb@...nel.org,
	hch@...radead.org
Cc:	martin.petersen@...cle.com, linux-scsi@...r.kernel.org,
	JBottomley@...allels.com, Sathya.Prakash@...adcom.com,
	suganath-prabu.subramani@...adcom.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/6] mpt3sas: Handle active cable exception event

On 6.5.2016 10:59, Chaitra P B wrote:
> In-order to handle this 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event,
> driver need to follow below steps,
> 1. Unmask the 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event,
> so that FW can notify this event to host driver.
> 2. After receiving this event, add this event to AEN event queue,
> for notifying this event to applications.
> 3. Then Print below message in kernel logs if the event data's reason
> code is zero,
> "Currently an active cable with ReceptacleID <ID_Value> cannot be powered
> and devices connected to this active cable will not be seen. This active
> cable requires <PowerValue_in_mW> of power"
>
> This event is only for Intruder/Cutlass HBAs.
>
> Signed-off-by: Chaitra P B <chaitra.basappa@...adcom.com>

Reviewed-by: Tomas Henzl <thenzl@...hat.com>

Tomas