From: Eric Dumazet <eric.dumazet@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] net: fix comment above build_skb()
Date: Tue, 23 Jul 2013 08:49:19 -0700 [thread overview]
Message-ID: <1374594559.3449.17.camel@edumazet-glaptop> (raw)
In-Reply-To: <1374593943-31642-1-git-send-email-f.fainelli@gmail.com>
On Tue, 2013-07-23 at 16:39 +0100, Florian Fainelli wrote:
> build_skb() specifies that the data parameter must come from a kmalloc'd
> area, this is only true if frag_size equals 0, because then build_skb()
> will use kzsize(data) to figure out the actual data size. Update the
> comment to reflect that special condition.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> net/core/skbuff.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index 20e02d2..d3174db 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -309,7 +309,8 @@ EXPORT_SYMBOL(__alloc_skb);
> * @frag_size: size of fragment, or 0 if head was kmalloced
> *
> * Allocate a new &sk_buff. Caller provides space holding head and
> - * skb_shared_info. @data must have been allocated by kmalloc()
> + * skb_shared_info. @data must have been allocated by kmalloc() only if
> + * @frag_size is 0.
> * The return is the new skb buffer.
> * On a failure the return is %NULL, and @data is not freed.
> * Notes :
Hmm, why not explaining the other case ? (frag_size > 0)
next prev parent reply other threads:[~2013-07-23 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 15:39 [PATCH] net: fix comment above build_skb() Florian Fainelli
2013-07-23 15:49 ` Eric Dumazet [this message]
2013-07-23 18:04 ` Florian Fainelli
2013-07-23 18:46 ` Ben Hutchings
2013-07-23 18:54 ` Eric Dumazet
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=1374594559.3449.17.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).