All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>, fw@strlen.de
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au,
	daniel@iogearbox.net, edumazet@google.com
Subject: Re: [PATCH RFC net-next] net: Assert napi_gro_cb size against skb->cb[]
Date: Fri, 31 Jul 2015 14:50:46 -0700	[thread overview]
Message-ID: <55BBEDB6.5050600@gmail.com> (raw)
In-Reply-To: <20150731.134442.1572308169975939249.davem@davemloft.net>

On 31/07/15 13:44, David Miller wrote:
> From: Florian Westphal <fw@strlen.de>
> Date: Fri, 31 Jul 2015 22:24:03 +0200
> 
>> Florian Fainelli <f.fainelli@gmail.com> wrote:
>>> On 64-bits hosts, napi_gro_cb is 48 bytes, which is exactly the size of
>>> skb->cb[], while on 32-bits hosts it is 36 bytes, but if it were to
>>> grow, we would not be catching a size inflation as we should.
>>> ---
>>>  net/core/dev.c | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/net/core/dev.c b/net/core/dev.c
>>> index 4870c3556a5a..20bc82604b75 100644
>>> --- a/net/core/dev.c
>>> +++ b/net/core/dev.c
>>> @@ -4115,6 +4115,8 @@ static void skb_gro_reset_offset(struct sk_buff *skb)
>>>  	const struct skb_shared_info *pinfo = skb_shinfo(skb);
>>>  	const skb_frag_t *frag0 = &pinfo->frags[0];
>>>  
>>> +	BUILD_BUG_ON(sizeof(skb->cb) < sizeof(struct napi_gro_cb));
>>
>> commit c3c7c254b2e8cd99b0adf288c2a1bddacd7ba255
>> already added a check for this.
> 
> Indeed.

Whoops, missed that part, thanks Florian!
-- 
Florian

      reply	other threads:[~2015-07-31 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 18:51 [PATCH RFC net-next] net: Assert napi_gro_cb size against skb->cb[] Florian Fainelli
2015-07-31 20:14 ` Tom Herbert
2015-07-31 20:24 ` Florian Westphal
2015-07-31 20:44   ` David Miller
2015-07-31 21:50     ` Florian Fainelli [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=55BBEDB6.5050600@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=herbert@gondor.apana.org.au \
    --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 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.