From: Alexander Aring <alex.aring@gmail.com>
To: alex.bluesman.smirnov@gmail.com
Cc: dbaryshkov@gmail.com, linux-zigbee-devel@lists.sourceforge.net,
netdev@vger.kernel.org, phoebe.buckheister@itwm.fraunhofer.de,
werner@almesberger.net, Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH net-next v2 0/2] 6lowpan: fragmentation fixes
Date: Mon, 2 Jun 2014 13:21:56 +0200 [thread overview]
Message-ID: <1401708118-16436-1-git-send-email-alex.aring@gmail.com> (raw)
This patch series fix the 6LoWPAN fragmentation which are in two cases broken.
The first case is if we have exactly two 6LoWPAN fragments only. This is fixed
by patch "6lowpan_rtnl: fix fragmentation with two fragments".
The second case is a off by one issue if we have payload which hits the fragment
boundary.
Both issues are introduced by commit d4b2816d67d6e07b2f27037f282d8db03a5829d7
("6lowpan: fix fragmentation").
Alexander Aring (2):
6lowpan_rtnl: fix fragmentation with two fragments
6lowpan_rtnl: fix off by one while fragmentation
net/ieee802154/6lowpan_rtnl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
1.9.3
next reply other threads:[~2014-06-02 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 11:21 Alexander Aring [this message]
2014-06-02 11:21 ` [PATCH net-next v2 1/2] 6lowpan_rtnl: fix fragmentation with two fragments Alexander Aring
[not found] ` <1401708118-16436-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-02 11:21 ` [PATCH net-next v2 2/2] 6lowpan_rtnl: fix off by one while fragmentation Alexander Aring
2014-06-02 17:40 ` [PATCH net-next v2 0/2] 6lowpan: fragmentation fixes 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=1401708118-16436-1-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=phoebe.buckheister@itwm.fraunhofer.de \
--cc=werner@almesberger.net \
/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).