Subject: Re: circular locking, mirred, 2.6.24.2

From: jamal <[email-masked]>
Date: Thu, 06 Mar 2008 08:59:55 -0500

On Thu, 2008-06-03 at 13:40 +0000, Jarek Poplawski wrote:

> I'm not sure this lockdep report is because of this, but there is
> really a problem with lock order while using sch_ingress with
> act_mirred: dev->queue_lock is taken after dev->ingress_lock, so
> reversely to e.g. qdisc_lock_tree(). This shouldn't be a problem
> when one of the devices is ifb yet.

Are there more details? Ingress of which netdevice is redirecting to
egress of which netdevice?
Sorry, I dont understand much about the internals of lockdep so i dont
know what you are teaching it in the patch below...

cheers,
jamal