On Mon, Feb 10, 2014 at 11:26:12AM -0800, Eric Dumazet wrote:
> On Mon, 2014-02-10 at 19:21 +0100, Alexander Aring wrote:
>
> > no problem. Maybe you can try to give me some explanation what you did
> > there?
> >
> > I see you make a lockdep_set_class for each tx queue and assign the
> > lowpan
On Mon, 2014-02-10 at 19:21 +0100, Alexander Aring wrote:
> no problem. Maybe you can try to give me some explanation what you did
> there?
>
> I see you make a lockdep_set_class for each tx queue and assign the
> lowpan_netdev_xmit_lock_key. So why it's better to make a own
> "lock_key".
This
Hi,
On Mon, Feb 10, 2014 at 10:16:26AM -0800, Eric Dumazet wrote:
> On Mon, 2014-02-10 at 18:33 +0100, Alexander Aring wrote:
> > Hi Eric,
> >
> > On Sun, Feb 09, 2014 at 04:41:47AM -0800, Eric Dumazet wrote:
> > >
> > > Please try the following fix, thanks for this report !
> > >
> > > diff --
On Mon, 2014-02-10 at 18:33 +0100, Alexander Aring wrote:
> Hi Eric,
>
> On Sun, Feb 09, 2014 at 04:41:47AM -0800, Eric Dumazet wrote:
> >
> > Please try the following fix, thanks for this report !
> >
> > diff --git a/net/ieee802154/6lowpan.c b/net/ieee802154/6lowpan.c
> > index 48b25c0af4d0..0
Hi Eric,
On Sun, Feb 09, 2014 at 04:41:47AM -0800, Eric Dumazet wrote:
>
> Please try the following fix, thanks for this report !
>
> diff --git a/net/ieee802154/6lowpan.c b/net/ieee802154/6lowpan.c
> index 48b25c0af4d0..069af33013c4 100644
> --- a/net/ieee802154/6lowpan.c
> +++ b/net/ieee802154
On Sun, 2014-02-09 at 11:20 +0100, Alexander Aring wrote:
> Hi,
>
> I got some locking issues with CONFIG_PROVE_LOCKING enabled and need help.
>
> Full output:
>
> =
> [ INFO: possible recursive locking detected ]
> 3.13.0-08605-g8f2b630-dirty #105 Not
Hi,
I got some locking issues with CONFIG_PROVE_LOCKING enabled and need help.
Full output:
=
[ INFO: possible recursive locking detected ]
3.13.0-08605-g8f2b630-dirty #105 Not tainted
-
agetty/841 is trying
