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:	Sun, 10 Jul 2011 01:45:35 +0100
From:	julie Sullivan <kernelmail.jms@...il.com>
To:	paulmck@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
	dipankar@...ibm.com, akpm@...ux-foundation.org,
	mathieu.desnoyers@...ymtl.ca, josh@...htriplett.org,
	niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, Valdis.Kletnieks@...edu, dhowells@...hat.com,
	eric.dumazet@...il.com, darren@...art.com, patches@...aro.org,
	torvalds@...ux-foundation.org
Subject: Re: PROBLEM: 3.0-rc kernels unbootable since -rc3

>Very good.  I have created a new jms.2011.07.07a branch in the -rcu
>git tree at:

I get my own branch! :-) (thanks for all your trouble with this.)

>Hello, Julie,

>Any news?

Sorry for the delay (again), I have to work very late Fridays and Saturdays.
Anyway, I have tested the six commits on my v3.0-rc4 branch (with
f8b7fc6b514f34a5 and a46e0899eec7a3069bc reverted) and can confirm
that they _all_ produce a bootable kernel at my end.

Btw, you may have noticed that my config has RCU_BOOST=n?
If I build a simple v3.0-rc4 kernel (ie one which includes the four
original commits (f8b7fc6b514, a46e0899eec, 09223371dea and
9a432736904)) but with RCU_BOOST=y it _will_ boot. I didn't know if
this was helpful or not.

If it is helpful, you probably know this, but in order to get
RCU_BOOST=y I have to change a couple of other configs - PREEMPT_RCU=y
(previously n) and to get PREEMPT_RCU=y, my preemption model has to be
'Preemptible Kernel (Low-Latency Desktop)' - PREEMPT=y (instead of
'Voluntary Kernel Preemption (Desktop)' - PREEMPT=n which it was
originally).

It's my day off tomorrow so I'll do some more testing (on -rc5 and
-rc6) (past 1.30am here in the UK now).

HTH,
Julie
--
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