From: Alexander Aring <alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
Cc: Martin Townsend
<mtownsend1973-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
linux-zigbee-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
BlueZ development
<linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Martin Townsend
<martin.townsend-I0Qfutc96jjQT0dZR+AlfA@public.gmane.org>,
Network Development
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Wireless"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/2] linux-wpan-next: lowpan_rcv - skb is freed within function and fix return values.
Date: Wed, 30 Jul 2014 20:27:40 +0200 [thread overview]
Message-ID: <20140730182738.GA21664@omega> (raw)
In-Reply-To: <C8606BA6-2918-4313-BEC5-FC3A377DE347-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
Hi Marcel,
On Wed, Jul 30, 2014 at 10:42:09AM -0700, Marcel Holtmann wrote:
> Hi Martin,
>
> > Currently it is up to the functions below lowpan_rcv to free the skb on error
> > conditions. This patch now removes all the UAPI error codes and process data
> > now returns -1 if there is a problem. In this scenario lowpan_rcv will free
> > the skb and return NET_RX_DROP. This also fixes the problem where
> > NET_RX_SUCCESS is returned on error
> >
> > Martin Townsend (2):
> > Remove dev parameter from skb_delivery_cb in 6lowpan.
> > Change lowpan_rcv so skb is freed within function and fix return
> > values.
> >
> > include/net/6lowpan.h | 4 ++--
> > net/6lowpan/iphc.c | 37 ++++++++++++++++++------------------
> > net/bluetooth/6lowpan.c | 21 ++++++++++-----------
> > net/ieee802154/6lowpan_rtnl.c | 44 +++++++++++++++++++++----------------------
> > 4 files changed, 52 insertions(+), 54 deletions(-)
>
> I can not take these patches at this point.
>
> checking file net/ieee802154/6lowpan_rtnl.c
> Hunk #1 FAILED at 143.
> Hunk #2 succeeded at 480 (offset -4 lines).
> 1 out of 2 hunks FAILED
>
> We need to get the IEEE 802.15.4 changes merged through John's wireless-next tree. IEEE 802.15.4 going straight into net-next and Bluetooth going into wireless-next will not work out smoothly when both technologies are now utilizing 6LoWPAN and we are heavily working on 6LoWPAN.
>
I already told Martin that these patches should be based on bluetooth
(better bluetooth-next, 802.15.4 hasn't a real stable strategie and there
are also some known other issues in the current implementation). I don't
think that the current implementation is used in a real environment.
I get this patch-series in a resend of this series, after Martin
subscribed the linux-zigbee-devel mailinglist, then I told Martin that I
need some time for review and he want to resend them tomorrow or friday.
The resend should based on bluetooth-next then, if this is okay for you.
I will cc bluetooth mailinglist in my review notes.
- Alex
next prev parent reply other threads:[~2014-07-30 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1406732105-17500-1-git-send-email-martin.townsend@xsilon.com>
2014-07-30 17:42 ` [PATCH 0/2] linux-wpan-next: lowpan_rcv - skb is freed within function and fix return values Marcel Holtmann
[not found] ` <C8606BA6-2918-4313-BEC5-FC3A377DE347-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2014-07-30 18:27 ` Alexander Aring [this message]
2014-07-30 18:32 ` Marcel Holtmann
2014-07-31 13:59 ` John W. Linville
[not found] ` <20140731135945.GB17560-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-07-31 14:07 ` Alexander Aring
2014-07-31 15:14 ` Marcel Holtmann
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=20140730182738.GA21664@omega \
--to=alex.aring-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-zigbee-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org \
--cc=martin.townsend-I0Qfutc96jjQT0dZR+AlfA@public.gmane.org \
--cc=mtownsend1973-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).