From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: Alasdair Kergon <agk@redhat.com>, Neil Brown <neilb@suse.de>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Cc: Lars Marowsky-Bree <lmb@suse.de>,
akpm@osdl.org, device-mapper development <dm-devel@redhat.com>
Subject: [PATCH 0/6] dm/md sysfs dependency tree (rev.3)
Date: Fri, 03 Mar 2006 19:45:50 -0500 [thread overview]
Message-ID: <4408E33E.1080703@ce.jp.nec.com> (raw)
Hello,
This is an updated version of dm/md sysfs dependency tree patch set.
For example, if dm-0 maps to sda, we'll have following symlinks;
/sys/block/dm-0/slaves/sda --> /sys/block/sda
/sys/block/sda/holders/dm-0 --> /sys/block/dm-0
Thanks for Alasdair, Neil and Greg for reviews and comments.
I think the patches get much better shape than before.
I'm happy to hear any other comments for these patches.
Patches included are:
1. [PATCH 1/6] kobject_add_dir
Adding kobject_add_dir() function which creates
a subdirectory for a given kobject.
2. [PATCH 2/6] add holders/slaves subdirectory to /sys/block
Creating "slaves" and "holders" directories in /sys/block/<disk>,
creating "holders" directory under /sys/block/<disk>/<partition>
3. [PATCH 3/6] bd_claim_by_kobject
Adding bd_claim_by_kobject() function which takes kobject as
additional signature of holder device and creates sysfs symlinks
between holder device and claimed device.
bd_release_from_kobject() is a counter part of bd_claim_by_kobject.
4. [PATCH 4/6] bd_claim_by_disk
Variants which take gendisk instead of kobject
and do kobject_{get,put}(&gendisk->kobj).
5. [PATCH 5/6] md to use bd_claim_by_disk
Use bd_claim_by_disk.
6. [PATCH 6/6] dm to use bd_claim_by_disk
Use bd_claim_by_disk.
Patches from 1 to 5 work both on 2.6.16-rc5 and 2.6.16-rc5-mm2.
I hope them to be included in mm if there's no problem.
Patch 6 depends on dm-table-store-md.patch in
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/.
The dm-table-store-md.patch might theoretically require some
locking/release-ordering fixes in dm core which is under
investigation though it's separate issue.
Thanks,
--
Jun'ichi Nomura, NEC Solutions (America), Inc.
next reply other threads:[~2006-03-04 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 0:45 Jun'ichi Nomura [this message]
2006-03-04 0:57 ` [PATCH 1/6] kobject_add_dir Jun'ichi Nomura
2006-03-04 0:57 ` [PATCH 2/6] add holders/slaves subdirectory to /sys/block Jun'ichi Nomura
2006-03-04 0:57 ` [PATCH 3/6] bd_claim_by_kobject Jun'ichi Nomura
2006-03-04 0:57 ` [PATCH 4/6] bd_claim_by_disk Jun'ichi Nomura
2006-03-04 0:58 ` [PATCH 5/6] md to use bd_claim_by_disk Jun'ichi Nomura
2006-03-04 0:58 ` [PATCH 6/6] dm " Jun'ichi Nomura
2006-03-06 15:56 ` Alasdair G Kergon
2006-03-06 17:00 ` Jun'ichi Nomura
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=4408E33E.1080703@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--cc=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=dm-devel@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).