linux-kernel - Re: [PATCH v2] ata: add AMD Seattle platform driver

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: <56A7A534.6040208@amd.com>
Date:	Tue, 26 Jan 2016 10:56:20 -0600
From:	Brijesh Singh <brijesh.singh@....com>
To:	Arnd Bergmann <arnd@...db.de>, Tejun Heo <tj@...nel.org>
CC:	<brijesh.singh@....com>, <linux-kernel@...r.kernel.org>,
	<hdegoede@...hat.com>, <linux-ide@...r.kernel.org>
Subject: Re: [PATCH v2] ata: add AMD Seattle platform driver

Hi Arnd,

On 01/26/2016 06:17 AM, Arnd Bergmann wrote:
> 
> I think it needs more work: The changelog describes it as a normal
> driver, but based on the previous discussion, this is just a hack
> to work around broken BIOS versions that can no longer be fixed in
> the field, and there has not been a decision what the proper
> representation should be in ACPI.
> 
I am not sure if we should label this driver as a hack to workaround the
broken BIOS. Unfortunately SoC did not implemented the enclosure management
per spec. Its not BIOS issue.

> The patch also fails to address the devicetree based case, even though
> we did come to a conclusion that the current behavior is a regression
> (compared to what we had in drivers/ide/) and that there is a relatively
> simple fix to do it right.
> 
I did looked at your recommendation for extending libahci to use ledtrig_ide_activity()
but as I pointed out in previous discussion this function is missing several key features
from EM (enclosure management) pov. e.g missing the slot number, missing the locate and fault led.
In case of EM, each port will have at least three leds (activity, locate and fault). 
Since these LED's are part of EM hence we need to ensure that tools like ledmon and ledctl (which uses libahci sysfs) works well.

The main question is, what is recommended approach to override libachi enclosure managements
transfer led messages function? A platform driver or something else.

Tejun and/or Hans do you have any recommendation ?


- Brijesh