From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH maint] batman-adv: Fix transmission of final, 16th fragment
Date: Mon, 13 Feb 2017 21:00:08 +0100 [thread overview]
Message-ID: <20170213200008.GK29718@otheros> (raw)
In-Reply-To: <20170213194431.24075-1-linus.luessing@c0d3.blue>
On Mon, Feb 13, 2017 at 08:44:31PM +0100, Linus Lüssing wrote:
> Trying to split and transmit a unicast packet in 16 parts will fail for
> the final fragment: After having sent the 15th one with a frag_packet.no
> index of 14, we will increase the the index to 15 - and return with an
> error code immediately, even though one more fragment is due for
> transmission and allowed.
>
> Fixing this issue by moving the check before incrementing the index.
>
> While at it, adding an unlikely(), because the check is actually more of
> an assertion.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
>
> ---
>
> Compile time tested only
> ---
> net/batman-adv/fragmentation.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/net/batman-adv/fragmentation.c b/net/batman-adv/fragmentation.c
> index 0854ebd..f181868 100644
> --- a/net/batman-adv/fragmentation.c
> +++ b/net/batman-adv/fragmentation.c
> @@ -499,6 +499,12 @@ int batadv_frag_send_packet(struct sk_buff *skb,
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?
next prev parent reply other threads:[~2017-02-13 20:00 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 [this message]
2017-02-13 21:23 ` Sven Eckelmann
2017-02-14 8:30 ` Linus Lüssing
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=20170213200008.GK29718@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.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.