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+55aFxdDBp5jg8W+BVpptP8DU9mziN7+wJPG=ihF2W=rFV1EA@mail.gmail.com>
Date:	Fri, 10 Jul 2015 10:11:18 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, vz@...ia.com,
	Tejun Heo <tj@...nel.org>, Ming Lei <ming.lei@...onical.com>,
	Shuah Khan <shuahkhan@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 4.2-rc1

On Fri, Jul 10, 2015 at 9:58 AM, Shuah Khan <shuahkh@....samsung.com> wrote:
>
> I am not sure why this patch would cause the problem I am seeing.
> This patch itself looks like a cleanup type patch and doesn't
> really fix a bug. I am building with this patch reverted at the
> moment to confirm.

Smells to me like it's just a timing issue, and that mayeb the bisect
failed because it's not 100% repeatable. Or maybe it *was* 100%
repeatable, but simply because that commit changed the timing of the
bootup scripts etc.

But yes, trying it with the revert in place is a good idea just to
make sure. And perhaps checking that kernel more than a few times to
verify just how repeatable it is.

           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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ