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]
Date:	Fri, 23 Oct 2009 13:03:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Erwan Velu <erwanaliasr1@...il.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH] dmi_check_system can generate Warnings when no DMI
	table is present


* Erwan Velu <erwanaliasr1@...il.com> wrote:

> When running the Linux Kernel, on some systems that doesn't have any DMI  
> table (like a Xen domU), some dmi_* calls can generates Warnings like :
>
>> / WARNING: at /usr/src/linux-2.6.29.1/drivers/firmware/dmi_scan.c:425/
>> / dmi_matches+0x7e/0x80()/
>> / dmi check: not initialized yet/

Empty DMI tables are common. What is not common is to call dmi_matches() 
before the DMI strings code has initialized.

> Some users reported this error : 
> http://lists.xensource.com/archives/html/xen-users/2009-04/msg00128.html 
> https://qa.mandriva.com/show_bug.cgi?id=54775

Looks like a Xen bug. DMI matching functions should be called after that 
code has initialized. The warning was added to catch such early calls.

Your patch works around that bug and the warning.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ