From: Eric Paris <eparis@parisplace.org>
To: David Miller <davem@davemloft.net>
Cc: jmorris@namei.org, latten@austin.ibm.com, selinux@tycho.nsa.gov,
netdev@vger.kernel.org, vyekkirala@TrustedCS.com
Subject: Re: [PATCH]: Add security check before flushing SAD/SPD
Date: Fri, 23 Mar 2007 14:50:31 -0400 [thread overview]
Message-ID: <1174675831.10788.79.camel@localhost.localdomain> (raw)
In-Reply-To: <20070323.114724.74563713.davem@davemloft.net>
On Fri, 2007-03-23 at 11:47 -0700, David Miller wrote:
> From: James Morris <jmorris@namei.org>
> Date: Fri, 23 Mar 2007 14:46:48 -0400 (EDT)
>
> > A 'flush' has a semantic implication that all entries will be removed, and
> > it should be atomic and either succeed or fail at that granularity.
>
> Correct.
Fair enough, does it matter that we have no way to report failure back
to users who can no longer assume success?
-Eric
next prev parent reply other threads:[~2007-03-23 18:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 18:35 [PATCH]: Add security check before flushing SAD/SPD Joy Latten
2007-03-22 19:01 ` David Miller
2007-03-22 21:23 ` Joy Latten
2007-03-22 23:49 ` James Morris
2007-03-22 23:50 ` Joy Latten
2007-03-23 0:56 ` James Morris
2007-03-23 5:39 ` Eric Paris
2007-03-23 6:22 ` David Miller
2007-03-23 16:33 ` Joy Latten
2007-03-23 16:59 ` Eric Paris
2007-03-23 18:50 ` Joy Latten
2007-03-23 18:46 ` James Morris
2007-03-23 18:47 ` David Miller
2007-03-23 18:50 ` Eric Paris [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-26 19:39 Joy Latten
2007-03-26 20:05 ` James Morris
2007-03-26 20:14 ` James Morris
2007-03-26 20:34 ` Eric Paris
2007-03-26 22:58 Joy Latten
2007-03-26 23:21 Joy Latten
2007-03-27 3:08 ` James Morris
2007-06-04 19:05 ` Eric Paris
2007-06-04 19:44 ` James Morris
2007-06-04 23:13 ` James Morris
2007-06-04 23:55 ` David Miller
2007-06-05 17:56 ` Joy Latten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1174675831.10788.79.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=latten@austin.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).