linux-kernel - Re: lockups shortly after booting in current git.

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:	Thu, 29 Mar 2012 13:59:33 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Ted Ts'o" <tytso@....edu>, Dave Jones <davej@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lockups shortly after booting in current git.

On Thu, Mar 29, 2012 at 1:39 PM, Ted Ts'o <tytso@....edu> wrote:
>
> I'd suggest restricting the bisect to fs/ first, and if that comes up
> with something non-sensical, you can always use the good/bad data
> points for a whole tree bisect.
>
> One commit that you might want to try testing is b43d17f31^, and see
> whether that works.  One potential commit that might be suspicious is
> b43d17f31 given the stack trace shows one process apparently waiting
> on PageWriteback.

Ahh, that does sound interesting and relevant.

Yeah, maybe the directed approach is worth it. In fact, considering
the above commie, maybe it might be worth it to be *very* directed,
and just test that one thing first, and maybe even skip the bisection
entirely and just test a revert if it looks promising.

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