From: David Miller <davem@davemloft.net>
To: akpm@osdl.org
Cc: netdev@vger.kernel.org, jmorris@namei.org
Subject: Re: [patch 5/9] secmark: Add secmark support to core networking.
Date: Fri, 09 Jun 2006 00:29:53 -0700 (PDT) [thread overview]
Message-ID: <20060609.002953.70217215.davem@davemloft.net> (raw)
In-Reply-To: <200606090520.k595KtAs032095@shell0.pdx.osdl.net>
From: akpm@osdl.org
Date: Thu, 08 Jun 2006 22:20:55 -0700
> Add a secmark field to the skbuff structure, to allow security subsystems to
> place security markings on network packets. This is similar to the nfmark
> field, except is intended for implementing security policy, rather than than
> networking policy.
>
> This patch was already acked in principle by Dave Miller.
>
> Signed-off-by: James Morris <jmorris@namei.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
Applied to net-2.6.18, thanks.
Remember James, you're on the hook now to shrink sk_buff
when you get a chance :-)
Thanks again.
next prev parent reply other threads:[~2006-06-09 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 5:20 [patch 5/9] secmark: Add secmark support to core networking akpm
2006-06-09 7:29 ` David Miller [this message]
2006-06-09 8:18 ` James Morris
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=20060609.002953.70217215.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=jmorris@namei.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox