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>] [day] [month] [year] [list]
Date:	Fri, 20 Aug 2010 23:44:38 -0400
From:	Mark Stanovich <mrktimber@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Linux 2.6.35.3

After updating to the 2.6.35.3 stable release, my machine was
rebooting automatically during the first few seconds of boot.

I bisected to the first bad commit of

commit 568132624386f53e87575195d868db
9afb2e9316
Author: H. Peter Anvin <hpa@...or.com>
Date:   Tue Jul 27 17:01:49 2010 -0700

    x86: Add memory modify constraints to xchg() and cmpxchg()

    commit 113fc5a6e8c2288619ff7e8187a6f556b7e0d372 upstream.

    xchg() and cmpxchg() modify their memory operands, not merely read
    them.  For some versions of gcc the "memory" clobber has apparently
    dealt with the situation, but not for all.

I noticed that the latest version pulled from Linus's git tree did not
have the problem.  After looking at the changes to
arch/x86/include/asm/cmpxchg_32.h, I cherry-picked two patches from
Linus's tree that seemed to make a difference, namely:

69309a05907546fb686b251d4ab041c26afe1e1d
4532b305e8f0c238dd73048068ff8a6dd1380291

Applying these patches solved the rebooting problem on 2.6.35.3

I believe the same problem also happens for the latest stable version
of 2.6.34, but did not verify the fix worked for the 2.6.34 stable
releases.

I don't know if this is helpful, but I thought I would let you know in
case someone else is having the same problem.

If you need any further information, just let me know.

    - Mark
--
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