From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] register_blkdev and unregister_blkdev
Date: Wed, 10 Oct 2001 15:53:27 +0530 [thread overview]
Message-ID: <3BC4219F.6020604@wipro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
I was looking at the code for register_blkdev and unregister_blkdev. I
found that no
locking (spinlocks) are used to protect the blkdevs struture in these
functions. I suspect
we have not seen a problem till now since
Either
1. register_blkdev is called from modules, and only module
initialization is protected.
2. register_blkdev is called during init time for drivers in the kernel
and I am not sure
about whether calls to register_blkdev at this time are implicitly
serialized, since only
1 CPU is active during initialization
Anway, what I needed to know was if (1) and (2) are enough to ensure
safety in register_blkdev
and unregister_blkdev.
May be I am missing something, there is already some lock which is held
before these routines
are invoked, I could not find any.
Comments
Thanks,
Balbir Singh.
[-- 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.
----------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2001-10-10 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 10:23 BALBIR SINGH [this message]
2001-10-10 10:34 ` [RFC] register_blkdev and unregister_blkdev Alexander Viro
2001-10-10 10:48 ` BALBIR SINGH
2001-10-10 10:53 ` Alexander Viro
2001-10-10 11:08 ` BALBIR SINGH
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=3BC4219F.6020604@wipro.com \
--to=balbir.singh@wipro.com \
--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