Linux Device Mapper development
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
	Michael Shigorin <mike@osdn.org.ua>,
	"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] libdm: add "|" to _is_whitelisted_char()
Date: Wed, 28 Nov 2012 13:50:39 +0100	[thread overview]
Message-ID: <50B6089F.6040603@redhat.com> (raw)
In-Reply-To: <50B5FDCD.2030605@redhat.com>

On 11/28/2012 01:04 PM, Peter Rajnoha wrote:
> Now, if you *really* intend to bypass this mangling and udev,
> you can use:
> 
>   dmsetup <dm_command> --manglename none ...
> 

If you use libdevmapper to handle device-mapper devices, have
a look at libdevmapper.h. You can bypass default mangling with
dm_set_name_mangling_mode(DM_STRING_MANGLING_NONE):

---
/*
 * Mangling support
 *
 * Character whitelist: 0-9, A-Z, a-z, #+-.:=@_
 * HEX mangling format: \xNN, NN being the hex value of the character.
 * (whitelist and format supported by udev)
*/
typedef enum {
        DM_STRING_MANGLING_NONE, /* do not mangle at all */
        DM_STRING_MANGLING_AUTO, /* mangle only if not already mangled with hex, error when mixed */
        DM_STRING_MANGLING_HEX   /* always mangle with hex encoding, no matter what the input is */
} dm_string_mangling_t;

/*
 * Set/get mangling mode used for device-mapper names and uuids.
 */
int dm_set_name_mangling_mode(dm_string_mangling_t name_mangling);
dm_string_mangling_t dm_get_name_mangling_mode(void);
---

Peter

      reply	other threads:[~2012-11-28 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 19:11 [PATCH] libdm: add "|" to _is_whitelisted_char() Michael Shigorin
2012-11-28 12:04 ` Peter Rajnoha
2012-11-28 12:50   ` Peter Rajnoha [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=50B6089F.6040603@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ldv@altlinux.org \
    --cc=mike@osdn.org.ua \
    --cc=vsu@altlinux.ru \
    /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