public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: "'LNML'" <linux-net@vger.kernel.org>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	netdev@oss.sgi.com
Subject: Re: catch 22 - porting net driver from 2.2 to 2.4
Date: Thu, 09 Nov 2000 12:37:21 -0500	[thread overview]
Message-ID: <3A0AE0D1.FB12725A@mandrakesoft.com> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B2708C@hasmsx52.iil.intel.com>

do_ioctl is inside rtnl_lock...

Remember if you need to alter the rules, you can always queue work in
the current context, and have a kernel thread handle the work.  The nice
thing about a kernel thread is that you start with a [almost] clean
state, when it comes to locks.

	Jeff


-- 
Jeff Garzik             |
Building 1024           | Would you like a Twinkie?
MandrakeSoft            |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-09 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 17:26 catch 22 - porting net driver from 2.2 to 2.4 Hen, Shmulik
2000-11-09 17:37 ` Jeff Garzik [this message]
2000-11-10  0:09 ` Olaf Titz
  -- strict thread matches above, loose matches on Subject: below --
2000-11-12 11:40 Hen, Shmulik
2000-11-12 12:20 ` Jeff Garzik
2000-11-12 11:48 Hen, Shmulik
2000-11-12 12:17 ` Jeff Garzik
2000-11-13  8:18 Hen, Shmulik
2000-11-13 17:09 Hen, Shmulik
2000-11-20 16:13 Hen, Shmulik

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=3A0AE0D1.FB12725A@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=shmulik.hen@intel.com \
    /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