From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Linearize fragment packets before merge
Date: Mon, 7 Feb 2011 00:24:59 +0100 [thread overview]
Message-ID: <201102070025.00197.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1296942118-4875-1-git-send-email-sven@narfation.org>
On Saturday 05 February 2011 22:41:58 Sven Eckelmann wrote:
> We access the data inside the skbs of two fragments directly using memmove
> during the merge. The data of the skb could span over multiple skb pages.
> An direct access without knowledge about the pages would lead to an
> invalid memory access.
Applied in revision 1933.
Thanks,
Marek
next prev parent reply other threads:[~2011-02-06 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 21:41 [B.A.T.M.A.N.] [PATCH] batman-adv: Linearize fragment packets before merge Sven Eckelmann
2011-02-06 23:24 ` Marek Lindner [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-07 23:59 [B.A.T.M.A.N.] pull request: batman-adv 2011-02-08 Sven Eckelmann
2011-02-07 23:59 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Linearize fragment packets before merge Sven Eckelmann
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=201102070025.00197.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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