From: Simon Horman <horms@verge.net.au>
To: Cong Wang <amwang@redhat.com>
Cc: netdev@vger.kernel.org, Ben Hutchings <bhutchings@solarflare.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next v3] net: clean up skb headers code
Date: Fri, 31 May 2013 09:25:17 +0900 [thread overview]
Message-ID: <20130531002517.GC26684@verge.net.au> (raw)
In-Reply-To: <1369879575-18701-1-git-send-email-amwang@redhat.com>
On Thu, May 30, 2013 at 10:06:15AM +0800, Cong Wang wrote:
> From: Cong Wang <amwang@redhat.com>
>
> commit 1a37e412a0225fcba5587 (net: Use 16bits for *_headers
> fields of struct skbuff) converts skb->*_header to u16,
> some #if NET_SKBUFF_DATA_USES_OFFSET are now useless,
> and to be safe, we could just use "X = ~(typeof(X))0;"
> as suggested by David and Ben.
>
> Cc: Ben Hutchings <bhutchings@solarflare.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Simon Horman <horms@verge.net.au>
> Signed-off-by: Cong Wang <amwang@redhat.com>
FWIW, I would prefer to see a patch that just removes the instances
of #ifdef NET_SKBUFF_DATA_USES_OFFSET below, and then a separate
patch to clean-up the use of ~0U once some consensus is reached on
the best approach.
The reason is that I suspect that the #ifdef NET_SKBUFF_DATA_USES_OFFSET
is a bug fix for cases where it is not defined. Whereas the ~0 discussion
is more cosmetic.
>
> ---
> v2: use typeof
> v3: use ~(typeof(X))0
>
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 5f93119..f3c18a0 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -1593,7 +1593,7 @@ static inline void skb_set_inner_mac_header(struct sk_buff *skb,
> }
> static inline bool skb_transport_header_was_set(const struct sk_buff *skb)
> {
> - return skb->transport_header != ~0U;
> + return skb->transport_header != ~(typeof(skb->transport_header))0;
> }
>
> static inline unsigned char *skb_transport_header(const struct sk_buff *skb)
> @@ -1636,7 +1636,7 @@ static inline unsigned char *skb_mac_header(const struct sk_buff *skb)
>
> static inline int skb_mac_header_was_set(const struct sk_buff *skb)
> {
> - return skb->mac_header != ~0U;
> + return skb->mac_header != ~(typeof(skb->mac_header))0;
> }
>
> static inline void skb_reset_mac_header(struct sk_buff *skb)
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index f45de07..e121c4b 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -199,9 +199,7 @@ struct sk_buff *__alloc_skb_head(gfp_t gfp_mask, int node)
> skb->truesize = sizeof(struct sk_buff);
> atomic_set(&skb->users, 1);
>
> -#ifdef NET_SKBUFF_DATA_USES_OFFSET
> - skb->mac_header = (__u16) ~0U;
> -#endif
> + skb->mac_header = ~(typeof(skb->mac_header))0;
> out:
> return skb;
> }
> @@ -275,10 +273,8 @@ struct sk_buff *__alloc_skb(unsigned int size, gfp_t gfp_mask,
> skb->data = data;
> skb_reset_tail_pointer(skb);
> skb->end = skb->tail + size;
> -#ifdef NET_SKBUFF_DATA_USES_OFFSET
> - skb->mac_header = (__u16) ~0U;
> - skb->transport_header = (__u16) ~0U;
> -#endif
> + skb->mac_header = ~(typeof(skb->mac_header))0;
> + skb->transport_header = ~(typeof(skb->transport_header))0;
>
> /* make sure we initialize shinfo sequentially */
> shinfo = skb_shinfo(skb);
> @@ -344,10 +340,8 @@ struct sk_buff *build_skb(void *data, unsigned int frag_size)
> skb->data = data;
> skb_reset_tail_pointer(skb);
> skb->end = skb->tail + size;
> -#ifdef NET_SKBUFF_DATA_USES_OFFSET
> - skb->mac_header = (__u16) ~0U;
> - skb->transport_header = (__u16) ~0U;
> -#endif
> + skb->mac_header = ~(typeof(skb->mac_header))0;
> + skb->transport_header = ~(typeof(skb->transport_header))0;
>
> /* make sure we initialize shinfo sequentially */
> shinfo = skb_shinfo(skb);
>
prev parent reply other threads:[~2013-05-31 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 2:06 [Patch net-next v3] net: clean up skb headers code Cong Wang
2013-05-30 11:18 ` David Laight
2013-05-30 20:16 ` David Miller
2013-05-30 21:05 ` Ben Hutchings
2013-05-31 0:18 ` Simon Horman
2013-05-31 0:25 ` Simon Horman [this message]
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=20130531002517.GC26684@verge.net.au \
--to=horms@verge.net.au \
--cc=amwang@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--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