From: Lou Langholtz <ldl@aros.net>
To: linux-kernel@vger.kernel.org
Subject: 2.5.70 add_disk(disk) re-registering disk->queue->elevator.kobj (bug?!)
Date: Tue, 03 Jun 2003 12:33:56 -0600 [thread overview]
Message-ID: <3EDCEA14.2000407@aros.net> (raw)
What am I missing (or is something in the block handling code actually
seriously wrong)?
In linux-2.5.70/drivers/block/genhd.c the add_disk(disk) logic seems
wrong because if disk->queue is shared by a few disk's, then that shared
queue's elevator is re-registered via the call to
elv_register_queue(disk) which calls down to
kobject_register(disk->queue->elevator.kobj). Or perhaps the block
handling logic was changed such that disks don't share the same
request_queue anymore. If so, then a few drivers (like nbd) need to be
updated to use a seperate request_queue per disk. If the block handling
code wasn't however changed this way though and struct gendisk objects
can still share the same request_queue then it seems a lot of other
logic todo with elv_register_queue() is also scrogged. Like shouldn't
disk->kobj.parent be set to kobject_get(&disk->queue->elevator.kobj)
instead of the reverse that the 2.5.70 code does? If so, then all the
deallocation code (called from del_gendisk(disk)) needs to be reversed
and changed around too. Seems like so much wrong logic that it's my
reading of the code that's at fault instead. Help!?
CC me on any email as I don't read the lkml regularly. ldl@aros.net
Thanks!!
Louis D. Langholtz
next reply other threads:[~2003-06-03 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 18:33 Lou Langholtz [this message]
2003-06-03 19:07 ` 2.5.70 add_disk(disk) re-registering disk->queue->elevator.kobj (bug?!) Andrew Morton
2003-06-04 0:29 ` Lou Langholtz
2003-06-04 0:56 ` viro
2003-06-04 16:08 ` Patrick Mochel
2003-06-04 1:00 ` Andrew Morton
2003-06-04 1:06 ` viro
2003-06-04 16:07 ` Lou Langholtz
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=3EDCEA14.2000407@aros.net \
--to=ldl@aros.net \
--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