From: Jarek Poplawski <jarkao2@o2.pl>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, jeff@garzik.org,
netdev@vger.kernel.org, jura@netams.com, paulus@samba.org
Subject: Re: [patch 04/13] ppp_generic: fix lockdep warning
Date: Mon, 14 May 2007 14:51:18 +0200 [thread overview]
Message-ID: <20070514125118.GA3382@ff.dom.local> (raw)
In-Reply-To: <20070514080829.GB2081@ff.dom.local>
On Mon, May 14, 2007 at 10:08:29AM +0200, Jarek Poplawski wrote:
> On Mon, May 14, 2007 at 09:28:45AM +0200, Jarek Poplawski wrote:
> > On Sun, May 13, 2007 at 11:39:37PM -0700, David Miller wrote:
> ...
> > > For each unique netdev type, use a different locking class.
> > >
> > > That will fix this forever, anything else is a situation specific
> > > band-aid (but then again isn't that what every lockdep annotation is
> > > :-).
...
> > Yes, this is very good idea, and I wonder, why you didn't try
> > this yourself (after my "ignore"). I thought a little about
> > this, but was afraid of it's wide range. Some things - like
> > in vlans - should be removed then, for this to work. I'll try
> > to send something like this soon (but I'm not so optimistic
> > it will cure all or forever...).
>
> So, because of this next planned patch (I hope not later than
> tomorrow), my two last patches for vlan and ppp_generic shouldn't
> be applied - their functionality will be moved to register_netdevice.
...or maybe not so easy... Here is the first problem: vlan does
register_netdevice(new_dev) with new_dev->type == real_dev->type,
so it still couldn't be recognized as something different from
the real ppp or eth. We need some trick... Probably we could
also think about using dev->name (or both), but there always would
be a problem with the size of a static table reserved for this.
So, now it seems something like my patch with lockdep class for ppp
could be settled with this, but more complex situations like vlan
still need special treatment.
Maybe we should also care not to go too far with this: I didn't read
other such reports recently, but here the problems seem to be made
mainly by some virtual devices without queues...
Jarek P.
next prev parent reply other threads:[~2007-05-14 12:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 5:52 [patch 04/13] ppp_generic: fix lockdep warning akpm
2007-05-11 20:57 ` Jeff Garzik
2007-05-11 21:03 ` David Miller
2007-05-11 21:12 ` Andrew Morton
2007-05-14 6:07 ` Jarek Poplawski
2007-05-14 6:39 ` David Miller
2007-05-14 7:28 ` Jarek Poplawski
2007-05-14 8:08 ` Jarek Poplawski
2007-05-14 12:51 ` Jarek Poplawski [this message]
2007-05-14 9:18 ` David Miller
2007-05-14 10:09 ` Jarek Poplawski
2007-05-15 5:31 ` [PATCH] netdev: lockdep classes in register_netdevice " Jarek Poplawski
2007-05-15 8:49 ` Yuriy N. Shkandybin
2007-05-15 10:05 ` Jarek Poplawski
2007-05-16 5:49 ` Jarek Poplawski
2007-05-15 8:50 ` Yuriy N. Shkandybin
2007-05-16 5:40 ` [PATCH (take 2)] " Jarek Poplawski
2007-05-16 5:47 ` David Miller
2007-05-16 6:17 ` Jarek Poplawski
2007-05-16 6:17 ` David Miller
2007-05-16 7:18 ` 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=20070514125118.GA3382@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jura@netams.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).