From: Sven Eckelmann <sven@narfation.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] pull request: batman-adv 2011-05-14
Date: Sun, 15 May 2011 00:16:32 +0200 [thread overview]
Message-ID: <1305411394-28807-1-git-send-email-sven@narfation.org> (raw)
Hi,
I would like tp propose following corrections for net-next-2.6/2.6.40.
Both are bug fixes. The first one fixes the regression introduced by
"batman-adv: Make bat_priv->primary_if an rcu protected pointer" which
prevented that the attached net_devices could be destroyed because the
references to them were incorrectly counted.
The second one is a bug which may "filled" the broadcast queue when at
the same time primary_if got changed and a broadcast was initiated. The
queue counter were never reduced because there were no actual packets
attached to the the queue.
thanks,
Sven
The following changes since commit 27aea2128ec09924dfe08e97739b2bf8b15c8619:
batman-adv: remove duplicate code from function is_bidirectional_neigh() (2011-05-08 16:10:42 +0200)
are available in the git repository at:
git://git.open-mesh.org/ecsv/linux-merge.git batman-adv/next
Marek Lindner (1):
batman-adv: reset broadcast flood protection on error
Sven Eckelmann (1):
batman-adv: Add missing hardif_free_ref in forw_packet_free
net/batman-adv/aggregation.c | 14 +++++++++++---
net/batman-adv/send.c | 19 ++++++++++++++++---
2 files changed, 27 insertions(+), 6 deletions(-)
next reply other threads:[~2011-05-14 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 22:16 Sven Eckelmann [this message]
2011-05-14 22:16 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Add missing hardif_free_ref in forw_packet_free Sven Eckelmann
2011-05-14 22:16 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: reset broadcast flood protection on error Sven Eckelmann
2011-05-15 2:51 ` [B.A.T.M.A.N.] pull request: batman-adv 2011-05-14 David Miller
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=1305411394-28807-1-git-send-email-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--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).