All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: martin@hundeboll.net
Subject: Re: [B.A.T.M.A.N.] [PATCH maint] batman-adv: Fix transmission of final, 16th fragment
Date: Tue, 14 Feb 2017 09:30:18 +0100	[thread overview]
Message-ID: <20170214083018.GL29718@otheros> (raw)
In-Reply-To: <3594207.H7EOxyrbqM@sven-edge>

On Mon, Feb 13, 2017 at 10:23:52PM +0100, Sven Eckelmann wrote:
> On Montag, 13. Februar 2017 21:00:08 CET Linus Lüssing wrote:
> [...]
> > And one more thing which seems fishy to me in this function:
> > 
> > 526         /* Make room for the fragment header. */
> > 527         if (batadv_skb_head_push(skb, header_size) < 0 ||
> > 528             pskb_expand_head(skb, header_size + ETH_HLEN, 0, GFP_ATOMIC) < 0) {
> > 529                 ret = -ENOMEM;
> > 530                 goto put_primary_if;
> > 531         }
> > 532 
> > 533         memcpy(skb->data, &frag_header, header_size);
> > 
> > 
> > For the pskb_expand_head() case, there is an skb_push(header_size) missing,
> > isn't it?
> 
> I am a little bit confused about your remark... and about the code.
> 
> So let's check what Martin wrote:
> 
>  * get header_size more room in our data section
>  * allocate new buffer to get header_size + ETH_HLEN in front (but not part)
>    of our data section
> 
> If one of these two fails then it will get in panic mode and leave the
> function.

Aiy, I'm sorry, misread that, you are right. Forget my remark.

  reply	other threads:[~2017-02-14  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 19:44 [B.A.T.M.A.N.] [PATCH maint] batman-adv: Fix transmission of final, 16th fragment Linus Lüssing
2017-02-13 20:00 ` Linus Lüssing
2017-02-13 21:23   ` Sven Eckelmann
2017-02-14  8:30     ` Linus Lüssing [this message]
2017-02-13 20:51 ` Sven Eckelmann
2017-02-21 17:27 ` Sven Eckelmann

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=20170214083018.GL29718@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=martin@hundeboll.net \
    /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.