From: Casey Schaufler <casey-iSGtlc1asvQWG2LlvL+J4A@public•gmane.org>
To: Eric Dumazet <eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>
Cc: Eric Paris <eparis-FjpueFixGhCM4zKIHC2jIg@public•gmane.org>,
Paul Moore <paul-r2n+y4ga6xFZroRs9YW3xA@public•gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>,
John Stultz <johnstul-r/Jw6+rmf7HQT0dZR+AlfA@public•gmane.org>,
"Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public•gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
James Morris
<james.l.morris-QHcLZuEGTsvQT0dZR+AlfA@public•gmane.org>,
selinux-+05T5uksL2qpZYMLLGbcSA@public•gmane.org,
john.johansen-Z7WLFzj8eWMS+FvcfC7Uqw@public•gmane.org,
LSM
<linux-security-module-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
Casey Schaufler <casey-iSGtlc1asvQWG2LlvL+J4A@public•gmane.org>
Subject: Re: [PATCH] ipv4: tcp: security_sk_alloc() needed for unicast_sock
Date: Thu, 09 Aug 2012 15:26:53 -0700 [thread overview]
Message-ID: <5024392D.3060608@schaufler-ca.com> (raw)
In-Reply-To: <1344549920.31104.701.camel@edumazet-glaptop>
On 8/9/2012 3:05 PM, Eric Dumazet wrote:
> On Thu, 2012-08-09 at 14:53 -0700, Casey Schaufler wrote:
>> On 8/9/2012 2:29 PM, Eric Dumazet wrote:
>>> smack_sk_alloc_security() uses smk_of_current(): What can be the
> I repeat: There are no true socket for these control packets.
OK, fine. You have an optimization. I'm good with that. Just don't
expect that the entire software stack you are taking advantage of
is going to change to accommodate your special case.
next prev parent reply other threads:[~2012-08-09 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50215A7E.8000701@linaro.org>
[not found] ` <1344462889.28967.328.camel@edumazet-glaptop>
[not found] ` <5022FD9A.4020603@schaufler-ca.com>
[not found] ` <1695034.0lrQgQPOMT@sifl>
2012-08-09 14:50 ` [PATCH] ipv4: tcp: security_sk_alloc() needed for unicast_sock Eric Dumazet
2012-08-09 15:07 ` Paul Moore
2012-08-09 15:36 ` Eric Dumazet
2012-08-09 15:59 ` Paul Moore
2012-08-09 16:05 ` Eric Paris
2012-08-09 16:09 ` Paul Moore
2012-08-09 17:46 ` Eric Dumazet
2012-08-09 20:06 ` Eric Paris
[not found] ` <CACLa4ptkvKj2GT4ZL+msMuWOHW885Hugk8nz3hvptOoY9-totw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-09 20:19 ` Paul Moore
2012-08-09 21:29 ` Eric Dumazet
2012-08-09 21:53 ` Casey Schaufler
2012-08-09 22:05 ` Eric Dumazet
2012-08-09 22:26 ` Casey Schaufler [this message]
2012-08-09 23:38 ` David Miller
2012-08-09 23:56 ` [PATCH] ipv4: tcp: unicast_sock should not land outside of TCP stack Eric Dumazet
2012-08-10 4:05 ` David Miller
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=5024392D.3060608@schaufler-ca.com \
--to=casey-isgtlc1asvqwg2llvl+j4a@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=eparis-FjpueFixGhCM4zKIHC2jIg@public$(echo .)gmane.org \
--cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=james.l.morris-QHcLZuEGTsvQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=john.johansen-Z7WLFzj8eWMS+FvcfC7Uqw@public$(echo .)gmane.org \
--cc=johnstul-r/Jw6+rmf7HQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=paul-r2n+y4ga6xFZroRs9YW3xA@public$(echo .)gmane.org \
--cc=selinux-+05T5uksL2qpZYMLLGbcSA@public$(echo .)gmane.org \
--cc=serge-A9i7LUbDfNHQT0dZR+AlfA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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