mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Mohammed Anees <pvmohammedanees2003@gmail.com>
Cc: Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	 dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm: Allow the use of escaped characters in str_field_delimit()
Date: Mon, 18 Nov 2024 11:38:05 +0100 (CET)	[thread overview]
Message-ID: <d62bac7e-432e-23bc-3d4c-d860e164dcaf@redhat.com> (raw)
In-Reply-To: <20241112175758.114080-1-pvmohammedanees2003@gmail.com>



On Tue, 12 Nov 2024, Mohammed Anees wrote:

> Escape characters were not handled before, which could lead to
> unwanted issues. Some device-mapper names may contain backslashes (`\`)
> as valid characters and should not be treated as escape characters. Only
> escape characters followed directly by the separator are considered
> valid and need to be processed. After handling, the escape characters
> are removed to ensure the final string is correctly parsed without
> unwanted escape sequences which were used only for escaping.
> 
> Signed-off-by: Mohammed Anees <pvmohammedanees2003@gmail.com>

Hi

Does anyone really need this? Is there some use case for using escape 
characters in device mapper names?

Mikulas

> ---
>  drivers/md/dm-init.c | 28 ++++++++++++++++++++++++----
>  1 file changed, 24 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/md/dm-init.c b/drivers/md/dm-init.c
> index b37bbe762500..dad9d523f7fb 100644
> --- a/drivers/md/dm-init.c
> +++ b/drivers/md/dm-init.c
> @@ -88,13 +88,33 @@ static void __init dm_setup_cleanup(struct list_head *devices)
>  static char __init *str_field_delimit(char **str, char separator)
>  {
>  	char *s;
> +	/* This variable handles removing escape characters, which are
> +	 * only used to avoid the separator and aren't needed in the
> +	 * final string.
> +	 */
> +	char *write;
>  
> -	/* TODO: add support for escaped characters */
>  	*str = skip_spaces(*str);
> -	s = strchr(*str, separator);
> +	s = *str;
> +	write = *str;
> +
> +	/* Find the separator and handle escape character */
> +	while (*s) {
> +		/* If '\' is followed by the separator, skip '\' by
> +		 * incrementing s, write will then overwrite the
> +		 * escape character with the separator.
> +		 */
> +		if (*s == '\\' && *(s + 1) != '\0' && *(s + 1) == separator)
> +			s++;
> +		else if (*s == separator)
> +			break;
> +
> +		*write++ = *s++;
> +	}
> +
>  	/* Delimit the field and remove trailing spaces */
> -	if (s)
> -		*s = '\0';
> +	if (write)
> +		*write = '\0';
>  	*str = strim(*str);
>  	return s ? ++s : NULL;
>  }
> -- 
> 2.47.0
> 


  parent reply	other threads:[~2024-11-18 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 17:57 Mohammed Anees
2024-11-13 10:39 ` Zdenek Kabelac
2024-11-18 10:38 ` Mikulas Patocka [this message]
2024-12-10 16:25   ` Mike Snitzer
2024-12-15 10:13     ` Mohammed Anees
2025-01-03 16:21       ` Mikulas Patocka
2025-01-06 21:27         ` Mike Snitzer

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=d62bac7e-432e-23bc-3d4c-d860e164dcaf@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvmohammedanees2003@gmail.com \
    --cc=snitzer@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

all inboxes | Powered by JetHome®