linux-kernel - Re: atomic RAM ?

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]

Message-ID: <20100414135704.3fc7b713@lxorguk.ukuu.org.uk>
Date:	Wed, 14 Apr 2010 13:57:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Michael Schnell <mschnell@...ino.de>
Cc:	nios2-dev <nios2-dev@...c.et.ntust.edu.tw>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: atomic RAM ?

> > FUTEX  ... is an implementation ...  for certain classes of processor.
> Alan,
> 
> If that is true "in depth", there should be no FUTEX-relevant  code,
> neither in the Kernel, nor in the library, that should be considered
> "arch-independent".

We have a lot of kernel code which is only usable on some architectures
and a few opt out of. The largest example of course being the mm layer
which is strictly for MMU equipped systems.

The important point is that you don't *have* to use futex to provide the
posix pthread lock primitives if they don't fit your platform.

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