From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] register_blkdev and unregister_blkdev
Date: Wed, 10 Oct 2001 16:38:49 +0530 [thread overview]
Message-ID: <3BC42C41.90809@wipro.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0110100651080.17790-100000@weyl.math.psu.edu>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Alexander Viro wrote:
>All module init code is under BKL and will stay that way for a long time.
>If that ever becomes not true, we are in for much more pain that
>register_blkdev() races - you would need to do audit of all drivers to
>pull something like that.
>
I suspected that the locking in init_module was preventing bad
things from happening in {devfs_}register_blkdev, I am sure now.
Balbir
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]
----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------
prev parent reply other threads:[~2001-10-10 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 10:23 [RFC] register_blkdev and unregister_blkdev BALBIR SINGH
2001-10-10 10:34 ` Alexander Viro
2001-10-10 10:48 ` BALBIR SINGH
2001-10-10 10:53 ` Alexander Viro
2001-10-10 11:08 ` BALBIR SINGH [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=3BC42C41.90809@wipro.com \
--to=balbir.singh@wipro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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