From: Pablo Neira <pablo@eurodev.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@oss.sgi.com, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/4] [NETLINK] introduce netlink_check_skb function
Date: Fri, 11 Feb 2005 22:31:40 +0100 [thread overview]
Message-ID: <420D243C.4090507@eurodev.net> (raw)
In-Reply-To: <20050211032448.GD31837@postel.suug.ch>
Thomas Graf wrote:
>>+/*
>>+ * Process one packet of messages.
>>+ * Malformed skbs with wrong lengths of messages are discarded silently.
>>+ */
>>+int netlink_process_skb(struct sk_buff *skb,
>>+ int (*process_msg)(struct sk_buff *skb,
>>+ struct nlmsghdr *nlh,
>>+ int *err))
>>+{
>>+ int err;
>>+ struct nlmsghdr * nlh;
>>+
>>+ while (skb->len >= NLMSG_SPACE(0)) {
>>
>>
>
>While you're at it, change that to NLMSG_LENGTH(0) or even to
>NLMSG_ALIGN(sizeof(*nlh)) to make it more readable. NLMSG_SPACE()
>represents the total size of a netlink message in the byte stream
>including the padding to payload in order to enforce proper
>alignement for successive netlink message header.
>
>
They are all the same thing. They all return 16 bytes which is the size
of a netlink header. If you and someone else think that those are more
readable, I'm ok with it, whatever. I just stole that piece of code as
is from current checkings done in xfrm and rtnetlink.
--
Pablo
next prev parent reply other threads:[~2005-02-11 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 0:14 [PATCH 2/4] [NETLINK] introduce netlink_check_skb function Pablo Neira
2005-02-11 3:24 ` Thomas Graf
2005-02-11 21:31 ` Pablo Neira [this message]
2005-02-11 22:43 ` Thomas Graf
2005-02-12 21:18 ` Pablo Neira
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=420D243C.4090507@eurodev.net \
--to=pablo@eurodev.net \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).