linux-kernel - Re: linux-next: Tree for Apr 9 [cpufreq: NULL pointer deref]

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUX2sqj+3hoxRvDDMMCz2Sne+QTeu3nc+zDw9P=EKwr1Tg@mail.gmail.com>
Date:	Tue, 9 Apr 2013 20:39:18 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	cpufreq@...r.kernel.org, Linux PM list <linux-pm@...r.kernel.org>,
	Thorsten Glaser <tg@...bsd.de>
Subject: Re: linux-next: Tree for Apr 9 [cpufreq: NULL pointer deref]

On Tue, Apr 9, 2013 at 8:29 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Tue, Apr 9, 2013 at 8:26 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
>>> On 9 April 2013 21:38, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>>> With x=3 the system gets in an unuseable state.
>>>>
>>>>      root# echo 0 > /sys/devices/system/cpu/cpu3/online
>>>>
>>>> I could not write my reply and had to do a hard/cold reboot.
>>>> The dmesg log I saw looked similiar to my digicam-shot.
>>>
>>> Few things i need from you. First is output of cpufreq-info. Then
>>> all the steps you did to reproduce above? Removed any other cpus?
>>>
>>> I am not able to find next-20130326 tag in my repo, only have 23 and 28.
>>> Can you debug it a bit to find exact line of code causing this issue using
>>> objdump?
>>>
>>> HINT: Documentation/BUG-HUNTING..
>>>
>>> Give me line numbers of both of these functions: __cpufreq_governor() and
>>> __cpufreq_remove_dev().
>>
>> I have recompiled next-20130326 and the REGRESSION is still reproducible.
>>
>> Attached are my dmesg, kernel-config, tarball of my drivers/cpufreq
>> build-dir, objdump of cpufreq_governor.o and the list of my current
>> amd64-toolchain.
>>
>> Hope this helps you!
>>
>> Regards,
>> - Sedat -
>
> $ cd linux-next/
>
> $ objdump --disassemble-all drivers/cpufreq/cpufreq.o >
> /tmp/cpufreq_o--disassemble-all.txt
>
> ...attached.
>
> - Sedat -

Hmm, I remembered Thorsten Glaser told be to pass also "-Mintel"
parameter ("-D" shortform for "--disassemble-all"):

$ objdump -D -Mintel drivers/cpufreq/cpufreq.o > /tmp/cpufreq_o-D-Mintel.txt

File attached.

Hope this helps you.

- Sedat -

View attachment "cpufreq_o-D-Mintel.txt" of type "text/plain" (196185 bytes)