All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	kernel@pengutronix.de, Simon Vincent <simon.vincent@xsilon.com>
Subject: Re: [PATCH bluetooth-next 4/4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header
Date: Wed, 24 Sep 2014 14:29:29 +0200	[thread overview]
Message-ID: <20140924122927.GC5246@omega> (raw)
In-Reply-To: <4472A049-A0BA-4E19-B788-5292749AD916@holtmann.org>

On Wed, Sep 24, 2014 at 02:18:52PM +0200, Marcel Holtmann wrote:
> Hi Alex,
> 
> > The 6lowpan ipv6 header compression was causing problems for other interfaces
> > that expected a ipv6 header to still be in place, as we were replacing the
> > ipv6 header with a compressed version. This happened if you sent a packet to a
> > multicast address as the packet would be output on 802.15.4, ethernet, and also
> > be sent to the loopback interface. The skb data was shared between these
> > interfaces so all interfaces ended up with a compressed ipv6 header.
> > The solution is to ensure that before we do any header compression we are not
> > sharing the skb or skb data with any other interface. If we are then we must
> > take a copy of the skb and skb data before modifying the ipv6 header.
> > The only place we can copy the skb is inside the xmit function so we don't
> > leave dangling references to skb.
> > This patch moves all the header compression to inside the xmit function. Very
> > little code has been changed it has mostly been moved from lowpan_header_create
> > to lowpan_xmit. At the top of the xmit function we now check if the skb is
> > shared and if so copy it. In lowpan_header_create all we do now is store the
> > source and destination addresses for use later when we compress the header.
> 
> so I added a two empty lines here to make this text a bit more easier on the eyes when reading it. Also in the future I would propose to keep it a 72 chars and not try to max out the 80 chars width. The reason is so that git log displays properly in a 80 chars terminal.
> 

ok. thanks. Yes, I know the 80 chars width... need to check this when I
see/apply others patches.

> > 
> > Signed-off-by: Simon Vincent <simon.vincent@xsilon.com>
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> > net/ieee802154/6lowpan_rtnl.c | 125 ++++++++++++++++++++++++++++++------------
> > 1 file changed, 89 insertions(+), 36 deletions(-)
> > 
> > diff --git a/net/ieee802154/6lowpan_rtnl.c b/net/ieee802154/6lowpan_rtnl.c
> > index 5e788cd..78cb206 100644
> > --- a/net/ieee802154/6lowpan_rtnl.c
> > +++ b/net/ieee802154/6lowpan_rtnl.c
> > @@ -71,20 +71,42 @@ struct lowpan_dev_record {
> > 	struct list_head list;
> > };
> > 
> > +/* don't save pan id, it's intra pan */
> > +struct lowpan_addr {
> > +	u8 mode;
> > +	union lowpan_addr_u {
> 
> I changed this into union { since there is no reason to name the union here.
> 

oops, yes you already said that at your first review note. Seems that
this wasn't changed.

Thanks Marcel.

- Alex

  reply	other threads:[~2014-09-24 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 10:21 [PATCH bluetooth-next 0/4] ieee802154: mrf24j40 cleanups and 6lowpan fix Alexander Aring
2014-09-24 10:21 ` [PATCH bluetooth-next 1/4] mrf24j40: fix Missing a blank line after declarations Alexander Aring
2014-09-24 10:21 ` [PATCH bluetooth-next 2/4] mrf24j40: remove unnecessary return statement Alexander Aring
2014-09-24 10:21 ` [PATCH bluetooth-next 3/4] mrf24j40: use pr_* / dev_* instead of printk() Alexander Aring
2014-09-24 10:21 ` [PATCH bluetooth-next 4/4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header Alexander Aring
2014-09-24 12:18   ` Marcel Holtmann
2014-09-24 12:29     ` Alexander Aring [this message]
2014-09-24 12:17 ` [PATCH bluetooth-next 0/4] ieee802154: mrf24j40 cleanups and 6lowpan fix 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=20140924122927.GC5246@omega \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=simon.vincent@xsilon.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.