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: <1207581866.21308.123.camel@localhost.localdomain>
Date:	Mon, 07 Apr 2008 08:24:26 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, takedakn@...data.co.jp,
	haradats@...data.co.jp
Subject: Re: [TOMOYO #7 02/30] Internal functions prototypes for SAKURA
	andTOMOYO.


On Mon, 2008-04-07 at 22:56 +0900, Tetsuo Handa wrote:

> I see. I'll move it on next posting.
> Although people advised me to use standard doubly linked list,
> TOMOYO wants to use singly linked list because the elements are append only.
> If TOMOYO is allowed to use singly linked list, it can make the source code read lock free.

I was just suggesting that you move your singly linked list operations
into list.h . There are some other places in the kernel that use singly
linked lists, but they have open coded operations (for instance
tasklets) ..

Daniel

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