linux-kernel - [RFC] Allow empty Trigger Error Action Table

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: <1326124184-10084-1-git-send-email-niklas.soderlund@ericsson.com>
Date:	Mon, 9 Jan 2012 16:49:43 +0100
From:	Niklas Söderlund <niklas.soderlund@...csson.com>
To:	lenb@...nel.org, ying.huang@...el.com, akpm@...ux-foundation.org
CC:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC] Allow empty Trigger Error Action Table 

When troubleshooting some BIOS code I encounter strange errors about firmware bugs. On closer inspection I found that the Trigger table returned from the firmware was empty but the header looked OK:

header_size = 16
table_size = 16
entry_count = 0

When looking at einj.c I found that this header would result in the error I was receiving. I took a quick look at the docs and from what I can tell this is a valid header, yes?

I don't know much about ACPI so I might be way off but the attached patch fix the error message for me (however I still can't detect the injected error but that might depend on my detection code or buggy firmware...)

Thanks
// Niklas

--
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/