linux-kernel - Re: Soft lockup during suspend since ~2.6.36 [bisected]

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: <BANLkTi=aED731W4WoKK1HUU88qR7RxpW6Q@mail.gmail.com>
Date:	Wed, 6 Apr 2011 08:03:26 +0200
From:	Thilo-Alexander Ginkel <thilo@...kel.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Soft lockup during suspend since ~2.6.36 [bisected]

On Wed, Apr 6, 2011 at 01:28, Arnd Bergmann <arnd@...db.de> wrote:
> On Tuesday 05 April 2011, Thilo-Alexander Ginkel wrote:
>> Thanks, that worked pretty well. A bisect with eleven builds later I
>> have now identified the following candidate commit, which may have
>> introduced the bug:
>>
>> dcd989cb73ab0f7b722d64ab6516f101d9f43f88 is the first bad commit
>> commit dcd989cb73ab0f7b722d64ab6516f101d9f43f88
>> Author: Tejun Heo <tj@...nel.org>
>> Date:   Tue Jun 29 10:07:14 2010 +0200
>
> Sorry, but looking at the patch shows that it can't possibly have introduced
> the problem, since all the code that is modified in it is new code that
> is not even used anywhere at that stage.
>
> As far as I can tell, you must have hit a false positive or a false negative
> somewhere in the bisect.

Well you're right. I hit "Reply" too early and should have paid closer
attention to what change the bisect actually brought up.

I already found a false negative (fortunately pretty close to the end
of the bisect sequence) and also verified the preceding good commits,
which gives me two new commits to test. I'll provide an update once
the builds and tests are through, which may however take until early
next week as I will be on vacation until then.

Regards,
Thilo
--
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/