linux-kernel - acerhdf: BIOS product mismatch due to whitespace

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: <2a6e8c0d0912052133v3e112bdbx2c95b17437bdd182@mail.gmail.com>
Date:	Sun, 6 Dec 2009 00:33:42 -0500
From:	"Ian E. Morgan" <penguin.wrangler@...il.com>
To:	Peter Feuerer <peter@...e.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: acerhdf: BIOS product mismatch due to whitespace

Peter,

Having just upgraded my AOA150 to 2.6.32, acerhdf was complaining:

acerhdf: Acer Aspire One Fan driver, v.0.5.18
acerhdf: unknown (unsupported) BIOS version Acer/AOA150
/v0.3310, please report, aborting!

DMI reports the product as "AOA150         " (i.e. 9 spaces after the
6-character model name). This causes the product match to fail, so I
had to use force_product="AOA150".

acerhdf: Acer Aspire One Fan driver, v.0.5.18
acerhdf: forcing BIOS product: AOA150

Then all was happy again. Any chance you could strip leading/trailing
whitespace in the product match to avoid this issue?

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