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: <201104060128.33887.arnd@arndb.de>
Date:	Wed, 6 Apr 2011 01:28:33 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Thilo-Alexander Ginkel" <thilo@...kel.com>
Cc:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Soft lockup during suspend since ~2.6.36 [bisected]

On Tuesday 05 April 2011, Thilo-Alexander Ginkel wrote:
> On Mon, Apr 4, 2011 at 17:32, Arnd Bergmann <arnd@...db.de> wrote:
> > On Monday 04 April 2011, Thilo-Alexander Ginkel wrote:
> >> ACK. I see two possibilities:
> >> a) The bug was introduced after the bisected bug was fixed
> >> b) The bug was already present earlier, but was masked by the bug from
> >> the bisected change
> >>
> >> I hope for a) as that would open the possibility to bisect this new bug.
> >
> > In case of b), you can still bisect it when you either apply the later fix
> > or revert the original patch whenever you build a kernel. Or you can try
> > to avoid using the usb-hid driver during bisect.
> 
> 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.

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