From: "Venkat Yekkirala" <vyekkirala@TrustedCS.com>
To: "'James Morris'" <jmorris@namei.org>,
"Herbert Xu" <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
"Paul Moore" <paul.moore@hp.com>
Subject: RE: [IPSEC] flow: Cache negative results
Date: Wed, 10 Jan 2007 09:26:06 -0600 [thread overview]
Message-ID: <001201c734cb$a64ba810$cc0a010a@tcssec.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701100913050.8582@d.namei>
> > So if the security folks actually care about this, they'd need to
> > flush the flow cache whenever a relevant change is made to the
> > security database.
I do not believe we are doing this. I will look into this ASAP.
next prev parent reply other threads:[~2007-01-10 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 7:22 [IPSEC] flow: Cache negative results Herbert Xu
2007-01-10 9:24 ` David Miller
2007-01-10 14:15 ` James Morris
2007-01-10 15:26 ` Venkat Yekkirala [this message]
2007-01-10 17:41 ` Venkat Yekkirala
2007-01-10 20:49 ` Herbert Xu
2007-01-10 21:08 ` Venkat Yekkirala
2007-01-10 23:27 ` Herbert Xu
2007-01-11 6:06 ` David Miller
2007-01-11 11:29 ` Herbert Xu
2007-01-10 16:11 ` Paul Moore
2007-01-10 23:27 ` Herbert Xu
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='001201c734cb$a64ba810$cc0a010a@tcssec.com' \
--to=vyekkirala@trustedcs.com \
--cc=davem@davemloft.net \
--cc=herbert.xu@redhat.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.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).