linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: DJBARROW@de.ibm.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: bug in /net/core/dev.c
Date: Tue, 12 Jun 2001 07:57:56 -0700 (PDT)	[thread overview]
Message-ID: <15142.11764.844524.381111@pizda.ninka.net> (raw)
In-Reply-To: <C1256A69.004E9AF2.00@d12mta09.de.ibm.com>
In-Reply-To: <C1256A69.004E9AF2.00@d12mta09.de.ibm.com>


DJBARROW@de.ibm.com writes:
 > On 390 it is very easy to hotplug devices under VM.
 > 
 > We do it all the time using the channel device layer on s/390, so users
 > can reconfigure devices if they misconfigure them.
 > 
 > If it can be registered it should be able to be unregistered.
 > 
 > Cornelia Huck in our group in boeblingen noticed the bug too.

I still think it's bogus.  Those "early init of device" messages
should only be occurring for specific legacy ISA device drivers,
and for nothing else.

You need to find a way to link in the S390 network drivers after the
net/ module so that the drivers run their init after net_dev_init()
runs.

Sure, this refcount thing is a bug, and I will look at your patch, but
you need to make your normal net devices get init'd after
net_dev_init() runs.

Later,
David S. Miller
davem@redhat.com

  reply	other threads:[~2001-06-12 14:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 14:17 DJBARROW
2001-06-12 14:57 ` David S. Miller [this message]
2001-06-12 15:34   ` Keith Owens
2001-06-12 15:46   ` David S. Miller
2001-06-12 16:11     ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-06-13 10:03 DJBARROW
2001-06-13 10:18 ` David S. Miller
2001-06-12 18:38 DJBARROW
2001-06-12 18:44 ` David S. Miller
2001-06-12 17:05 Ulrich.Weigand
2001-06-12 17:20 ` Keith Owens
2001-06-12 16:43 DJBARROW
2001-06-12 16:51 ` David S. Miller
2001-06-12 17:02 ` Keith Owens
2001-06-11 18:32 DJBARROW
2001-06-12  3:18 ` David S. Miller

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=15142.11764.844524.381111@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=DJBARROW@de.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: bug in /net/core/dev.c' \
    /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

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).