linux-kernel - Re: [ANNOUNCE] 3.0-rt4 , Follow up question

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>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1107281253451.2660@ionos>
Date:	Thu, 28 Jul 2011 18:27:27 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Lars Segerlund <lars.segerlund@...il.com>
cc:	linux-rt-users <linux-rt-users@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt4 , Follow up question

On Thu, 28 Jul 2011, Lars Segerlund wrote:
> How much is there left to do for mainline inclusion ?
> 
> A rough guess would be nice, just to assess the amount of work and severity.

  http://dilbert.com/strips/comic/2010-06-26/

If that doesn't answer your question, then you might try:

   # tar -xjf patches-3.0-rtx.tar.bz2
   # ls patches/*.patch
   # wc -l patches/*.patch
   # for each patch in patches; do read $patch; done

> As I understand it , a lot of subsystes are trying to go lockless, so
> things should become easier.

Not really, they just use different mechanisms. Serialization and
synchronization are not restricted to locks and some of these
mechanisms are even more evil than a plain old lock.

Thanks,

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