From: Casey Schaufler <casey@schaufler-ca.com>
To: David Miller <davem@davemloft.net>
Cc: fw@strlen.de, paul@paul-moore.com, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
casey@schaufler-ca.com
Subject: Re: New skb extension for use by LSMs (skb "security blob")?
Date: Thu, 22 Aug 2019 15:34:44 -0700 [thread overview]
Message-ID: <5d524e45-0d80-3a1c-4fd2-7610d2197bf8@schaufler-ca.com> (raw)
In-Reply-To: <20190822.152857.1388207414767202364.davem@davemloft.net>
On 8/22/2019 3:28 PM, David Miller wrote:
> From: Casey Schaufler <casey@schaufler-ca.com>
> Date: Thu, 22 Aug 2019 14:59:37 -0700
>
>> Sure, you *can* do that, but it would be insane to do so.
> We look up the neighbour table entries on every single packet we
> transmit from the kernel in the same exact way.
>
> And it was exactly to get rid of a pointer in a data structure.
I very much expect that the lifecycle management issues would
be completely different, but I'll admit to having little understanding
of the details of the neighbour table.
next prev parent reply other threads:[~2019-08-22 22:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 22:00 New skb extension for use by LSMs (skb "security blob")? Paul Moore
2019-08-21 22:50 ` David Miller
2019-08-22 3:27 ` Paul Moore
2019-08-22 3:54 ` David Miller
2019-08-22 18:50 ` Casey Schaufler
2019-08-22 7:03 ` Florian Westphal
2019-08-22 16:32 ` Paul Moore
2019-08-22 20:10 ` Casey Schaufler
2019-08-22 20:15 ` Florian Westphal
2019-08-22 20:35 ` Casey Schaufler
2019-08-22 21:18 ` David Miller
2019-08-22 21:59 ` Casey Schaufler
2019-08-22 22:28 ` David Miller
2019-08-22 22:34 ` Casey Schaufler [this message]
2019-08-22 22:36 ` David Miller
2019-08-23 18:56 ` Casey Schaufler
2019-08-22 21:17 ` 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=5d524e45-0d80-3a1c-4fd2-7610d2197bf8@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.