All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	kernel@pengutronix.de, Martin Townsend <mtownsend1973@gmail.com>
Subject: Re: [PATCHv3 bluetooth-next 3/3] 6lowpan: nhc: add other known rfc6282 compressions
Date: Wed, 10 Dec 2014 13:04:56 +0100	[thread overview]
Message-ID: <20141210120453.GA24018@omega> (raw)
In-Reply-To: <1418212574.32209.78.camel@jrissane-mobl.ger.corp.intel.com>

Hi Jukka,

On Wed, Dec 10, 2014 at 01:56:14PM +0200, Jukka Rissanen wrote:
> 
> Found the problem, in bt 6lowpan the skb that was freed was still used
> by network stack. I will send a patch for this soon.
> 

ok.

> > 
> > > 
> > > > > 
> > > > > Do this please on one node, the other node should send some 6LoWPAN IPHC
> > > > > packets to check if the error handling working there.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Another issue is that I see that skb->dev isn't set before calling
> > > > > lowpan_header_decompress. Because inside your log is a "NULL":
> > > > > 
> > > > > (NULL net_device): received unknown nhc id which was not found.
> > > > > 
> > > > > Can you change that? That skb->dev is set to before calling
> > > > > lowpan_header_decompress.
> > > > 
> > > > I am setting the skb->dev after the call to lowpan_header_decompress().
> > > > And anyway the skb->dev is only used when printing the err.
> > > > Actually should we replace the skb->dev in lowpan_header_decompress()
> > > > with plain dev as that is given to the function as a parameter. 
> > > > 
> > > 
> > > Ok, how we introduce this now? You wanna add this do the patch series for
> > > fixing the above issue, or should I add it to my patch series for
> > > introduce nhc framework?
> > 
> > I am fine with either. If you have time, please go ahead and send a
> > patch or I can do it also after figuring what is causing the crash.
> 
> After second though, can you do the change as actually what I had in
> mind was to change the
> 
>       netdev_warn(skb->dev, ...)
> to
>       netdev_warn(dev, ...)
> 
> and that code is part of patch 2 of your patchset.
> 
> Another thing I noticed is that we need to rate limit the output as now
> it might be that the warning is printed for every udp packet which is
> way too much.
> 

ok. Or maybe simple remove the output, or make it only visable on
debugging. I don't really know what's the best notice for use that the
packet was dropping because invalid/unsupported packets.

I will do it to ratelimit and add patches for the netdev_warn(dev, ...)
thing. Currently I am working a little bit on the 802154 branch again.

I will start this work when you are done with the above fix.

- Alex

      reply	other threads:[~2014-12-10 12:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 15:50 [PATCHv3 bluetooth-next 0/3] 6lowpan: introduce nhc framework Alexander Aring
2014-12-08 15:50 ` [PATCHv3 bluetooth-next 1/3] 6lowpan: add generic nhc layer interface Alexander Aring
2014-12-08 15:50 ` [PATCHv3 bluetooth-next 2/3] 6lowpan: add udp compression via nhc layer Alexander Aring
2014-12-08 15:50 ` [PATCHv3 bluetooth-next 3/3] 6lowpan: nhc: add other known rfc6282 compressions Alexander Aring
2014-12-09 11:28   ` Jukka Rissanen
2014-12-09 11:40     ` Jukka Rissanen
2014-12-09 11:52     ` Alexander Aring
2014-12-09 14:05       ` Jukka Rissanen
2014-12-09 18:42         ` Alexander Aring
2014-12-10  9:04           ` Jukka Rissanen
2014-12-10 11:56             ` Jukka Rissanen
2014-12-10 12:04               ` Alexander Aring [this message]

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=20141210120453.GA24018@omega \
    --to=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mtownsend1973@gmail.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.