public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Martin Hundebøll" <martin@hundeboll.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Sven Eckelmann <sven@narfation.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH-maint] batman-adv: Calculate extra tail size based on queued fragments
Date: Mon, 01 Dec 2014 12:37:19 +0100	[thread overview]
Message-ID: <547C52EF.2060908@hundeboll.net> (raw)
In-Reply-To: <1417426330-9178-1-git-send-email-sven@narfation.org>

Hi Sven,

Thanks for looking into this!

On 2014-12-01 10:32, Sven Eckelmann wrote:
> The fragmentation code was replaced in 9b3eab61754d74a93c9840c296013fe3b4a1b606
> ("batman-adv: Receive fragmented packets and merge"). The new code provided a
> mostly unused parameter skb for the merging function. It is used inside the
> function to calculate the additionally needed skb tailroom. But instead of
> increasing its own tailroom, it is only increasing the tailroom of the first
> queued skb. This is not correct in some situations because the first queued
> entry can be a different one than the parameter.
>
> An observed problem was:
>
> 1. packet with size 104, total_size 1464, fragno 1 was received
>     - packet is queued
> 2. packet with size 1400, total_size 1464, fragno 0 was received
>     - packet is queued at the end of the list
> 3. enough data was received and can be given to the merge function
>     (1464 == (1400 - 20) + (104 - 20))
>     - merge functions gets 1400 byte large packet as skb argument
> 4. merge function gets first entry in queue (104 byte)
>     - stored as skb_out
> 5. merge function calculates the required extra tail as total_size - skb->len
>     - pskb_expand_head tail of skb_out with 64 bytes
> 6. merge function tries to squeeze the extra 1380 bytes from the second queued
>     skb (1400 byte aka skb parameter) in the 64 extra tail bytes of skb_out
>
> Instead calculate the extra required tail bytes for skb_out also using skb_out
> instead of using the parameter skb. The skb parameter is only used to get the
> total_size from the last received packet. This is also the total_size used to
> decide that all fragments were received.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> Reported-by: Philipp Psurek <philipp.psurek@gmail.com>
> ---
> This is a minimized version which doesn't require the patch
> "[PATCH-maint] batman-adv: Check total_size when reassembling fragments".
> ---
>   fragmentation.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fragmentation.c b/fragmentation.c
> index f14e54a..af16844 100644
> --- a/fragmentation.c
> +++ b/fragmentation.c
> @@ -247,7 +247,7 @@ batadv_frag_merge_packets(struct hlist_head *chain, struct sk_buff *skb)
>   	kfree(entry);
>
>   	/* Make room for the rest of the fragments. */
> -	if (pskb_expand_head(skb_out, 0, size - skb->len, GFP_ATOMIC) < 0) {
> +	if (pskb_expand_head(skb_out, 0, size - skb_out->len, GFP_ATOMIC) < 0) {
>   		kfree_skb(skb_out);
>   		skb_out = NULL;
>   		goto free;
>

I noticed the same mistake, when looking into Philipp's issue, but 
couldn't make wrap my head around it (as to why it should cause the 
crash). Your description makes sense, and I think my mistake was to 
forget the inverse tx/rx of fragments.

Anyways:
Acked-by: Martin Hundebøll <martin@hundeboll.net>
+45 61 65 54 61
martin@hundeboll.net

  reply	other threads:[~2014-12-01 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  9:32 [B.A.T.M.A.N.] [PATCH-maint] batman-adv: Calculate extra tail size based on queued fragments Sven Eckelmann
2014-12-01 11:37 ` Martin Hundebøll [this message]
2014-12-08  3:39 ` Marek Lindner

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=547C52EF.2060908@hundeboll.net \
    --to=martin@hundeboll.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sven@narfation.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