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-02-08
Date: Tue, 8 Feb 2011 00:59:20 +0100 [thread overview]
Message-ID: <1297123161-25612-1-git-send-email-sven@narfation.org> (raw)
Hi,
I would like to propose following patch for net-2.6.git/2.6.38 which fixes a
possible kernel oops in the unicast fragmentation code.
thanks,
Sven
The following changes since commit 1181e1daace88018b2ff66592aa10a4791d705ff:
batman-adv: Make vis info stack traversal threadsafe (2011-01-30 10:32:08 +0100)
are available in the git repository at:
git://git.open-mesh.org/ecsv/linux-merge.git batman-adv/merge
Sven Eckelmann (1):
batman-adv: Linearize fragment packets before merge
net/batman-adv/unicast.c | 15 ++++++++++-----
1 files changed, 10 insertions(+), 5 deletions(-)
next reply other threads:[~2011-02-07 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 23:59 Sven Eckelmann [this message]
2011-02-07 23:59 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Linearize fragment packets before merge Sven Eckelmann
2011-02-08 3:55 ` [B.A.T.M.A.N.] pull request: batman-adv 2011-02-08 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=1297123161-25612-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).