mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: kuznet@ms2.inr.ac.ru, jgarzik@mandrakesoft.com,
	linux-kernel@vger.kernel.org
Subject: Re: NETDEV_CHANGE events when __LINK_STATE_NOCARRIER is modified
Date: Tue, 15 May 2001 04:15:11 -0700 (PDT)	[thread overview]
Message-ID: <15105.4031.414577.452451@pizda.ninka.net> (raw)
In-Reply-To: <3B010C64.556758D8@uow.edu.au>
In-Reply-To: <3B006F84.C1427EB3@uow.edu.au> <200105150902.NAA29079@ms2.inr.ac.ru> <3B010C64.556758D8@uow.edu.au>


Andrew Morton writes:
 > > Again, BKL has nothing to do with this (and ioctl does not hold it)
 > 
 > asmlinkage long sys_ioctl(unsigned int fd, unsigned int cmd, unsigned long arg)
 > {       
 >         struct file * filp;
 >         unsigned int flag;
 >         int on, error = -EBADF;
 > 
 >         filp = fget(fd);
 >         if (!filp)
 >                 goto out;
 >         error = 0;
 >         lock_kernel();
 > 
 > The CPU running ifconfig spins here.

Alexey's brain is going through net/socket.c:sock_ioctl() :-)

There we drop the kernel lock...

Later,
David S. Miller
davem@redhat.com

      parent reply	other threads:[~2001-05-15 11:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15091.23655.488243.650394@pizda.ninka.net>
2001-05-13 18:19 ` kuznet
2001-05-14  1:43   ` Andrew Morton
2001-05-14 17:47     ` kuznet
2001-05-14 18:12       ` Jeff Garzik
2001-05-14 18:40         ` kuznet
2001-05-14 19:27           ` Jeff Garzik
2001-05-14 19:42             ` kuznet
2001-05-14 20:34               ` Jeff Garzik
2001-05-14 23:51           ` Andrew Morton
2001-05-15  9:02             ` kuznet
2001-05-15 11:00               ` Andrew Morton
2001-05-15 11:15               ` David S. Miller [this message]

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=15105.4031.414577.452451@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=andrewm@uow.edu.au \
    --cc=jgarzik@mandrakesoft.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®