netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Benny Amorsen <benny+usenet@amorsen.dk>,
	Chuck Ebbert <cebbert@redhat.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH take2] Re: Nested VLAN causes recursive locking error
Date: Thu, 10 Jan 2008 16:31:22 +0100	[thread overview]
Message-ID: <47863A4A.6070303@trash.net> (raw)
In-Reply-To: <20080102234107.GA6902@ami.dom.local>

Jarek Poplawski wrote:
> As a matter of fact I started to doubt it's a real problem: 2 vlan
> headers in the row - is it working?

Yes, apparently some people are using this.

> Anyway, as Patrick pointed, the previous patch was a bit buggy, and
> deeper nesting needs a little more (if it's can work too...). So,
> here is something minimal.
> 
> Patrick, if you think about something else, then of course don't care
> about this patch.

No, this seems fine, thanks. Even better would be a way to get
the last lockdep subclass through lockdep somehow, but I couldn't
find a clean way for this. So I've applied your patch and also
fixed macvlan.



  reply	other threads:[~2008-01-10 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 23:03 Nested VLAN causes recursive locking error Chuck Ebbert
2007-12-20 13:52 ` [PATCH] " Jarek Poplawski
2007-12-31 15:04   ` Patrick McHardy
2007-12-31 17:45     ` Jarek Poplawski
2007-12-31 17:54       ` Jarek Poplawski
2007-12-31 21:59       ` Jarek Poplawski
2008-01-02 16:40   ` Benny Amorsen
2008-01-02 23:41     ` [PATCH take2] " Jarek Poplawski
2008-01-10 15:31       ` Patrick McHardy [this message]
2008-01-10 21:08         ` Jarek Poplawski
2008-01-10 21:33           ` Jarek Poplawski

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=47863A4A.6070303@trash.net \
    --to=kaber@trash.net \
    --cc=benny+usenet@amorsen.dk \
    --cc=cebbert@redhat.com \
    --cc=jarkao2@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).