Dne 12. 11. 24 v 18:57 Mohammed Anees napsal(a):
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@xxxxxxxxx>
---
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)
{
There is libdevmapper project (ATM distirbuted through lvm2 project) which
is handling the management of name & uuid with mangling - so they are properly
visible on systems with udev.
IMHO this escape handling does not belong to kernel and is rather related to
the actual user space running on top.
Regards
Zdenek
