Quoting Serge E. Hallyn ([EMAIL PROTECTED]):
From cd7c384f76d2c0f6b12a1c0936d54ae9c5e7cb4c Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn [EMAIL PROTECTED]
Date: Fri, 19 Oct 2007 15:39:10 -0400
Subject: [PATCH RFC] capabilities: fix compilation with strict type checking
(v2)
Since at
From cd7c384f76d2c0f6b12a1c0936d54ae9c5e7cb4c Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn [EMAIL PROTECTED]
Date: Fri, 19 Oct 2007 15:39:10 -0400
Subject: [PATCH RFC] capabilities: fix compilation with strict type checking
(v2)
Since at least 1998 the code under STRICT_CAP_T_TYPECHECKS option
On 10/18/07, Al Viro [EMAIL PROTECTED] wrote:
On Thu, Oct 18, 2007 at 05:57:05AM +0100, Al Viro wrote:
On Tue, Oct 16, 2007 at 09:17:40PM -0700, Casey Schaufler wrote:
Think what happens if CPU1 adds to list and CPU2 sees write to smk_known
*before* it sees write to -smk_next. We see a
