b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: [PATCH 0/2] pull request for net: batman-adv 2019-08-30
Date: Fri, 30 Aug 2019 09:25:00 +0200	[thread overview]
Message-ID: <20190830072502.16929-1-sw@simonwunderlich.de> (raw)

Hi David,

here is another small batman-adv pull request for net.

Please pull or let me know of any problem!

Thank you,
      Simon

The following changes since commit 3ee1bb7aae97324ec9078da1f00cb2176919563f:

  batman-adv: fix uninit-value in batadv_netlink_get_ifindex() (2019-08-14 19:27:07 +0200)

are available in the Git repository at:

  git://git.open-mesh.org/linux-merge.git tags/batadv-net-for-davem-20190830

for you to fetch changes up to 0ff0f15a32c093381ad1abc06abe85afb561ab28:

  batman-adv: Only read OGM2 tvlv_len after buffer len check (2019-08-23 18:20:31 +0200)

----------------------------------------------------------------
Here are two batman-adv bugfixes:

 - Fix OGM and OGMv2 header read boundary check,
   by Sven Eckelmann (2 patches)

----------------------------------------------------------------
Sven Eckelmann (2):
      batman-adv: Only read OGM tvlv_len after buffer len check
      batman-adv: Only read OGM2 tvlv_len after buffer len check

 net/batman-adv/bat_iv_ogm.c | 20 +++++++++++++-------
 net/batman-adv/bat_v_ogm.c  | 18 ++++++++++++------
 2 files changed, 25 insertions(+), 13 deletions(-)

             reply	other threads:[~2019-08-30  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  7:25 Simon Wunderlich [this message]
2019-08-30  7:25 ` [PATCH 1/2] batman-adv: Only read OGM tvlv_len after buffer len check Simon Wunderlich
2019-08-30  7:25 ` [PATCH 2/2] batman-adv: Only read OGM2 " Simon Wunderlich
2019-08-31 20:18 ` [PATCH 0/2] pull request for net: batman-adv 2019-08-30 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=20190830072502.16929-1-sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --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).