All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Antonio Quartulli <ordex@autistici.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org,
	Marek Lindner <lindner_marek@yahoo.de>,
	stable@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 stable 3.5] batman-adv: Fix broadcast packet CRC calculation
Date: Mon, 5 Nov 2012 09:15:40 +0100	[thread overview]
Message-ID: <20121105081540.GA3657@kroah.com> (raw)
In-Reply-To: <1351991127-10420-1-git-send-email-ordex@autistici.org>

On Sun, Nov 04, 2012 at 02:05:27AM +0100, Antonio Quartulli wrote:
> From: Linus Lüssing <linus.luessing@web.de>
> 
> commit 7f112af40fecf5399b61e69ffc6b55a9d82789f7 upstream.
> 
> So far the crc16 checksum for a batman-adv broadcast data packet, received
> on a batman-adv hard interface, was calculated over zero bytes of its
> content leading to many incoming broadcast data packets wrongly being
> dropped (60-80% packet loss).
> 
> This patch fixes this issue by calculating the crc16 over the actual,
> complete broadcast payload.
> 
> The issue is a regression introduced by
> ("batman-adv: add broadcast duplicate check").
> 
> Signed-off-by: Linus Lüssing <linus.luessing@web.de>
> Acked-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
> Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
> Signed-off-by: Antonio Quartulli <ordex@autistici.org>
> ---
> 
> Sorry, but I made a mistake in backporting the patch to 3.5. Now it's ok.
> Thanks,

3.5 is end-of-life, so I can't take any patches for it anymore, sorry.
In the future, take a look at the front page of www.kernel.org, it shows
what trees are still "alive" and which are end-of-life.

thanks,

greg k-h

      reply	other threads:[~2012-11-05  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-03 20:55 [B.A.T.M.A.N.] [PATCH stable 3.5] batman-adv: Fix broadcast packet CRC calculation Antonio Quartulli
2012-11-04  1:05 ` [B.A.T.M.A.N.] [PATCHv2 " Antonio Quartulli
2012-11-05  8:15   ` Greg KH [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=20121105081540.GA3657@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=lindner_marek@yahoo.de \
    --cc=ordex@autistici.org \
    --cc=stable@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.