Re: [PATCH] Re: Nested VLAN causes recursive locking error

[Patrick McHardy <kaber@trash.net>]

Jarek Poplawski wrote:
> diff -Nurp linux-2.6.24-rc5-/net/8021q/vlan.c linux-2.6.24-rc5+/net/8021q/vlan.c
> --- linux-2.6.24-rc5-/net/8021q/vlan.c	2007-12-17 13:29:19.000000000 +0100
> +++ linux-2.6.24-rc5+/net/8021q/vlan.c	2007-12-20 14:21:02.000000000 +0100
> @@ -307,12 +307,15 @@ int unregister_vlan_device(struct net_de
>  	return ret;
>  }
>  
> +#ifdef CONFIG_LOCKDEP
>  /*
>   * vlan network devices have devices nesting below it, and are a special
>   * "super class" of normal network devices; split their locks off into a
>   * separate class since they always nest.
>   */
>  static struct lock_class_key vlan_netdev_xmit_lock_key;
> +static int subclass; /* vlan nesting vlan */
> +#endif
>  
>  static const struct header_ops vlan_header_ops = {
>  	.create	 = vlan_dev_hard_header,
> @@ -349,7 +352,14 @@ static int vlan_dev_init(struct net_devi
>  		dev->hard_start_xmit = vlan_dev_hard_start_xmit;
>  	}
>  
> -	lockdep_set_class(&dev->_xmit_lock, &vlan_netdev_xmit_lock_key);
> +#ifdef CONFIG_LOCKDEP
> +	if ((real_dev->priv_flags & IFF_802_1Q_VLAN) &&
> +	    subclass < MAX_LOCKDEP_SUBCLASSES - 1)
> +		subclass++;
> +

That will increment the subclass globally, but it should actually just
use real_dev->subclass + 1. Otherwise we'll permenently fail after
registering 8 nested devices and unregistering them again.