From: Nikolay Borisov <n.borisov@siteground.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Getting mapped device namw
Date: Mon, 06 Jul 2015 12:49:56 +0300 [thread overview]
Message-ID: <559A4F44.6050200@siteground.com> (raw)
In-Reply-To: <DUB115-W711C5EDD3B9DD92DCD95F796930@phx.gbl>
On 07/06/2015 12:40 PM, Gili B wrote:
> Thanks
> hash_cell is defined privately in dm_ioctl.c , so I cannot access it.
The beauty of open source software is that you can always export it for
you own needs :)
> also dm_get_mdptr ,is not extern so I can't access it neither.
The function is exposed via device_mapper.h so you can just include this
header. Poke the code around you might come up with an even better idea.
But generally you wouldn't want to use the name the user provided.
Instead, use the name of the block device being created e.g. dm-1. This
can be obtained from the dm_get_device function and using the dm_dev struct
>
> Thanks
> -gili
>
>> Date: Mon, 6 Jul 2015 12:32:33 +0300
>> From: kernel@kyup.com
>> To: dm-devel@redhat.com
>> Subject: Re: [dm-devel] Getting mapped device namw
>>
>>
>> On 07/06/2015 12:20 PM, Gili B wrote:
>>> hi
>>> when a user run :
>>> dmsetup create [device name] ....
>>> Can a device mapper target find out the device name that the user entered ?
>>
>> Apparently the name is being associated with a hash_cell object, which
>> in turn is associated with struct mapped_device in dm_hash_insert
>> (called from dev_create, which is invoked as part of the create IOCTL).
>> So presumably if you get an instance of struct mapped_device and then
>> invoke dm_get_mdptr(md). What you'd get is a pointer to struct hash_cell
>>
>>> I need it for creating entries in proc for example.
>>>
>>> Thanks
>>> -gili
>>>
>>>
>>>
>>>
>>> --
>>> dm-devel mailing list
>>> dm-devel@redhat.com
>>> https://www.redhat.com/mailman/listinfo/dm-devel
>>>
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
next prev parent reply other threads:[~2015-07-06 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 9:20 Getting mapped device namw Gili B
2015-07-06 9:32 ` Nikolay Borisov
2015-07-06 9:40 ` Gili B
2015-07-06 9:49 ` Nikolay Borisov [this message]
2015-07-08 5:56 ` Gili B
2015-07-06 11:20 ` Zdenek Kabelac
2015-07-06 12:04 ` Gili B
2015-07-06 12:19 ` Zdenek Kabelac
2015-07-07 6:22 ` Gili B
2015-07-07 6:30 ` Zdenek Kabelac
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=559A4F44.6050200@siteground.com \
--to=n.borisov@siteground.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.