linux-kernel - Re: [PATCH] Fix segfault when printing battery status

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:	Mon, 19 Nov 2007 14:09:51 +0300
From:	Alexey Starikovskiy <aystarik@...il.com>
To:	Rolf Eike Beer <eike-kernel@...tec.de>
CC:	lenb@...nel.org, linux-acpi@...r.kernel.org, astarikovskiy@...e.de,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix segfault when printing battery status

Rolf Eike Beer wrote:
> Alexey Starikovskiy wrote:
>   
>> Rolf Eike Beer wrote:
>>     
>>> cat
>>> /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:19/PNP0C0A:00/power_
>>> supply/BAT1/status
>>>
>>> This leads to a stacktrace as acpi_battery_get_property() returns 0 for a
>>> case where it does not set val->intval. These value is used as an array
>>> index in
>>> drivers/power/power_supply_sysfs.c::power_supply_show_property(). I had a
>>> situation where the value was 4096 which caused a problem as the array
>>> only has 5 entries.
>>>
>>> Signed-off-by: Rolf Eike Beer <eike-kernel@...tec.de>
>>>       
>> Rolf, thanks for remainding.
>>     
>
> Huh? This one is unrelated to the problem I reported two weeks ago...
>
> Eike
>   
You are second to send the same patch, first one I already acked.
But it seems that Len did not pick it up yet.
Look for "ACPI: Always return valid 'status' from 
acpi_battery_get_property()"
if interested...

Regards,
Alex.

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