From: Jamal Hadi Salim <hadi@cyberus.ca>
To: paul.moore@hp.com
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [RFC 6/8] NetLabel: CIPSOv4 integration
Date: Fri, 28 Jul 2006 07:54:30 -0400 [thread overview]
Message-ID: <1154087670.5165.36.camel@jzny2> (raw)
In-Reply-To: <20060622225410.521216000@flek.zko.hp.com>
On Thu, 2006-22-06 at 18:49 -0400, paul.moore@hp.com wrote:
> plain text document attachment (netlabel-cipsov4)
> Add CIPSO/IPv4 support and management to the NetLabel subsystem. These changes
> integrate the CIPSO/IPv4 configuration into the existing NetLabel code and
> enable the use of CIPSO/IPv4 within the overall NetLabel framework.
> ---
> net/netlabel/netlabel_cipso_v4.c | 583 +++++++++++++++++++++++++++++++++++++++
> 1 files changed, 583 insertions(+)
>
> +/**
> + * netlbl_cipsov4_rcv - Process incoming NetLabel packets
> + * @skb: the NETLINK buffer
> + * @msg: pointer to the start of the NetLabel data
> + *
> + * Description:
> + * This function is reponsibile for reading all of the incoming CIPSO V4
> + * NetLabel traffic and dispatching it to the correct CIPSO V4 functions.
> + *
> + */
> +void netlbl_cipsov4_rcv(const struct sk_buff *skb, const unsigned char *msg)
> +{
> + int ret_val;
> + struct netlbl_cipsov4_msghdr *nl_cv4_hdr;
> +
> + if (nlmsg_len((struct nlmsghdr *)skb->data) <
> + sizeof(struct netlbl_cipsov4_msghdr)) {
> + netlbl_cipsov4_send_ack(skb, EINVAL);
> + return;
> + }
> +
> + nl_cv4_hdr = (struct netlbl_cipsov4_msghdr *)msg;
> + switch (nl_cv4_hdr->opcode) {
> + case NL_CV4_ADD:
Could you not have had all these NL_CV4_CMDs as just TLVs?
This is just the classical way of how we do things.
This would allow you to send multiple cmds in one message as well as
very easily add new ones in the future.
BTW, can you please repost your latest changes to netdev?
cheers,
jamal
next prev parent reply other threads:[~2006-07-28 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 22:49 [RFC 0/8] Minor update to allow a "sane review" paul.moore
2006-06-22 22:49 ` [RFC 1/8] NetLabel: documentation paul.moore
2006-06-22 22:49 ` [RFC 2/8] NetLabel: core network changes paul.moore
2006-06-22 22:49 ` [RFC 3/8] NetLabel: CIPSOv4 engine paul.moore
2006-06-22 22:49 ` [RFC 4/8] NetLabel: core NetLabel subsystem paul.moore
2006-06-22 22:49 ` [RFC 5/8] NetLabel: SELinux support paul.moore
2006-06-22 22:49 ` [RFC 6/8] NetLabel: CIPSOv4 integration paul.moore
2006-07-28 11:54 ` Jamal Hadi Salim [this message]
2006-07-28 18:10 ` Paul Moore
2006-06-22 22:49 ` [RFC 7/8] NetLabel: unlabeled packet handling paul.moore
2006-06-22 22:49 ` [RFC 8/8] NetLabel: tie NetLabel into the Kconfig system paul.moore
-- strict thread matches above, loose matches on Subject: below --
2006-06-27 22:56 [RFC 0/8] NetLabel: updated to use generic netlink paul.moore
2006-06-27 22:56 ` [RFC 6/8] NetLabel: CIPSOv4 integration paul.moore
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=1154087670.5165.36.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--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).