From: Dave Hansen <haveblue@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: devfs: BKL *not* taken while opening devices
Date: Mon, 29 Apr 2002 10:52:13 -0700 [thread overview]
Message-ID: <3CCD884D.70009@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0204291937430.23113-100000@serv>
Roman Zippel wrote:
> The BKL doesn't make a driver safe, remember that it's released on
> schedule.
Not safe, but _safer_, and definitely safe enough for almost all uses.
Some of the drivers rely on the fact that open() cannot be run
concurrently. The BKL does provide this if open never blocks.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-04-29 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 13:13 devfs: BKL *not* taken while opening devices Russell King
2002-04-29 15:30 ` Dave Hansen
2002-04-29 17:21 ` Arjan van de Ven
2002-04-29 17:40 ` Roman Zippel
2002-04-29 17:46 ` Arjan van de Ven
2002-05-02 16:44 ` Alan Cox
2002-04-29 17:52 ` Dave Hansen [this message]
2002-04-30 12:45 ` Russell King
2002-04-30 16:42 ` Dave Hansen
2002-04-30 16:52 ` Arjan van de Ven
2002-04-30 16:58 ` Dave Hansen
2002-04-30 18:26 ` Martin J. Bligh
2002-04-30 17:03 ` Russell King
2002-05-11 0:45 ` Richard Gooch
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=3CCD884D.70009@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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