From: Antonio Quartulli <antonio@meshcoding.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: pull request net: 20140515
Date: Thu, 15 May 2014 20:50:48 +0200 [thread overview]
Message-ID: <1400179852-4064-1-git-send-email-antonio@meshcoding.com> (raw)
Hello David,
our debugging campaign continues..
Here I have another small set of fixes intended for net/linux-3.15 and *stable*
(please enqueue them).
I know we already sent some fixes and we are running late in the rc cycle, but,
as you can see from the stats below, the changes are very very small.
Patch 1 prevents a NULL dereference in batadv_orig_hardif_seq_print_text() along
the failure path.
Patch 2 fixes a reference counting imbalance that gets triggered everytime the
batman packet fragmentation mechanism is used; this imbalance prevents the
netdev object held by batman-adv from being released on shutdown.
Patch 3 fixes the reference counting for the orig_node objects in order to avoid
any access after they have been free'd.
Patch 4 fixes the TT local check in DAT (Distributed ARP Table) that is used to
avoid sending (self-forged) ARP replies on behalf of other host in the LAN.
Please pull or let me know of any problem!
Thanks a lot,
Antonio
The following changes since commit e84d2f8d2ae33c8215429824e1ecf24cbca9645e:
net: filter: s390: fix JIT address randomization (2014-05-14 16:10:16 -0400)
are available in the git repository at:
git://git.open-mesh.org/linux-merge.git tags/batman-adv-fix-for-davem
for you to fetch changes up to cc2f33860cea0e48ebec096130bd0f7c4bf6e0bc:
batman-adv: fix local TT check for outgoing arp requests in DAT (2014-05-15 20:23:47 +0200)
----------------------------------------------------------------
Include changes:
- fix NULL dereference in batadv_orig_hardif_seq_print_text()
- fix reference counting imbalance when using fragmentation
- avoid access to orig_node objects after they have been free'd
- fix local TT check for outgoing arp requests in DAT
----------------------------------------------------------------
Antonio Quartulli (3):
batman-adv: fix reference counting imbalance while sending fragment
batman-adv: increase orig refcount when storing ref in gw_node
batman-adv: fix local TT check for outgoing arp requests in DAT
Marek Lindner (1):
batman-adv: fix indirect hard_iface NULL dereference
net/batman-adv/distributed-arp-table.c | 3 +--
net/batman-adv/fragmentation.c | 11 ++++++++---
net/batman-adv/gateway_client.c | 11 +++++++++--
net/batman-adv/originator.c | 3 ++-
4 files changed, 20 insertions(+), 8 deletions(-)
next reply other threads:[~2014-05-15 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 18:50 Antonio Quartulli [this message]
2014-05-15 18:50 ` [PATCH 1/4] batman-adv: fix indirect hard_iface NULL dereference Antonio Quartulli
2014-05-15 18:50 ` [PATCH 2/4] batman-adv: fix reference counting imbalance while sending fragment Antonio Quartulli
2014-05-15 18:50 ` [PATCH 3/4] batman-adv: increase orig refcount when storing ref in gw_node Antonio Quartulli
2014-05-15 18:50 ` [PATCH 4/4] batman-adv: fix local TT check for outgoing arp requests in DAT Antonio Quartulli
2014-05-16 20:29 ` pull request net: 20140515 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=1400179852-4064-1-git-send-email-antonio@meshcoding.com \
--to=antonio@meshcoding.com \
--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).