linux-kernel - Re: [DOC PATCH] Remove mention of semaphores from kernel-locking

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

Message-ID: <20080421165405.GB20637@parisc-linux.org>
Date:	Mon, 21 Apr 2008 10:54:05 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Peter Zijlstra <peterz@...radead.org>,
	Jonathan Corbet <corbet@....net>
Subject: Re: [DOC PATCH] Remove mention of semaphores from kernel-locking

On Tue, Apr 22, 2008 at 02:15:30AM +1000, Rusty Russell wrote:
> >     <title>Three Main Types of Kernel Locks: Spinlocks, Mutexes and
> > Semaphores</title>
> >
> >     <para>
> > -     There are three main types of kernel locks.  The fundamental type
> > +     There are two main types of kernel locks.  The fundamental type
> >       is the spinlock
> >       (<filename class="headerfile">include/asm/spinlock.h</filename>),
> >       which is a very simple single-holder lock: if you can't get the
> 
> Fix title, too?

Heh.  Oops, thanks.

> Thanks for the other fixes too; this document needs some love,

No problem ... I started out augmenting it to discuss semaphores and
mutexes properly and realised I'd totally overloaded this document with
detail.  I'm tempted to rip the RCU pieces out of this document and
create a new one.  What we currently have just doesn't read nicely [1],
but this is a project for another day.

> Acked,
> Rusty.

I'll add your ack.  Thanks!

[1] This seems to be a common problem in Linux's Documentation/ directory
... just _read_ CodingStyle and you can tell which bits are Linus'
(funny, deprecating, suggestions) and which bits were added later
(stern, prescriptive, fascist).  The later bits break the flow of the
document and I find them quite jarring.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/