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
| ||
|
Date: Wed, 18 Aug 2010 13:34:56 +0800 From: Huang Ying <ying.huang@...el.com> To: Jin Dongming <jin.dongming@...css.fujitsu.com>, Lu Yinghai <yinghai@...nel.org> Cc: Randy Dunlap <randy.dunlap@...cle.com>, Stephen Rothwell <sfr@...b.auug.org.au>, Andi Kleen <andi@...stfloor.org>, Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>, ACPI <linux-acpi@...r.kernel.org>, LKLM <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/4] [Patch-next] ACPI, APEI, ERST Fix the wrong checking of Serialization Header's length On Tue, 2010-08-17 at 12:44 +0800, Jin Dongming wrote: > (2010/08/17 12:22), Huang Ying wrote: > > On Tue, 2010-08-17 at 10:14 +0800, Jin Dongming wrote: > >>> I don't think it is necessary to change the header definition, and > >>> seri_header is not a good name for me. > >> Why I added this structure here is that I don't want to do following checking. > >> For example, > >> if (header_length != 0x0c) { > >> ... > >> } > > > > This can be: > > > > static int erst_check_table(struct acpi_table_erst *erst_tab) > > { > > - if (erst_tab->header_length != sizeof(struct acpi_table_erst)) > > + if (erst_tab->header_length != > > + (sizeof(struct acpi_table_erst) - sizeof(erst_tab->header))) > > > > like Yinghai has been done. > > > Yes. It looks good. And I am sorry I am unaware of Yinghai' patch. Maybe you can help push this fix in, it seems that Yinghai is busy on something else? Hi, Yinghai, Do you mind for Dongming to push this fix? Best REgards, Huang Ying -- 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/
Powered by blists - more mailing lists