linux-kernel - Re: small regression: hwmon: (applesmc) Check key count before proceeding

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: <5291CA7B.3080904@euromail.se>
Date:	Sun, 24 Nov 2013 10:44:27 +0100
From:	Henrik Rydberg <rydberg@...omail.se>
To:	Michele Baldessari <michele@...syn.org>
CC:	jwboyer@...oraproject.org, Guenter Roeck <linux@...ck-us.net>,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org,
	bugzilla@...orremedies.com, Chris Murphy <chris@...rf.com>
Subject: Re: small regression: hwmon: (applesmc) Check key count before proceeding
 - 5f4513864304672e6ea9eac60583eeac32e679f2

Hi Michele,

> The issue Chris has seen in Fedora on one MacBookPro4,1
> (https://bugzilla.redhat.com/show_bug.cgi?id=1033414) is that this
> machine returns a huge number from read_register_count() so now we will
> try to allocate an insane amount of memory and we will barf:
> [    8.603053] applesmc: key count changed from 261 to 1392508929

I was under the impression that this machine was tested before, and that

commit 25f2bd7f5add608c1d1405938f39c96927b275ca
Author: Henrik Rydberg <rydberg@...omail.se>
Date:   Wed Oct 2 19:15:03 2013 +0200

    hwmon: (applesmc) Always read until end of data

resolved this problem? But if the kernel under test is 3.11.8, both patches are
already present... Chris, could you please sched some light on this before
moving on?

Thanks,
Henrik

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