From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Sreeraj S Kurup <sreekuttan2156239@gmail.com>, tiwai@suse.de
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, tiwai@suse.com
Subject: Re: [PATCH v3] ALSA: control: Fix parsing of numeric fields
Date: Sun, 08 Nov 2026 17:48:09 +0100 [thread overview]
Message-ID: <eb3ce9e09ea5f06c427247e8c93e6e1649ac77ba.camel@mailbox.org> (raw)
In-Reply-To: <20261108124832.3058-1-sreekuttan2156239@gmail.com>
On Sun, 2026-11-08 at 12:48 +0000, Sreeraj S Kurup wrote:
> parse_uint() passes the remaining input string to kstrtoull().
>
> When the input contains comma-separated fields, the string
> contains both the numeric value and the following fields.
>
> For example, with:
>
> device=1,subdevice=0,name=Master
>
> kstrtoull() receives "1,subdevice=0,name=Master" and fails
> to parse the numeric value.
>
> Stop parsing at the next comma and pass only the numeric
> field to kstrtouint().
>
> This allows numeric fields to be parsed correctly in
> comma-separated input.
>
> Fixes: a135dfb5de15 ("ALSA: led control - add sysfs kcontrol LED marking layer")
> Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
Reviewed-by: Manuel Ebner
> ---
> v3:
> - No code changes. Retain the v2 implementation after
> comparing the alternative approaches.
> v2:
> - Add the Fixes trailer.
>
> sound/core/control_led.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/sound/core/control_led.c b/sound/core/control_led.c
> index 501387287ae6..3f54af2cb505 100644
> --- a/sound/core/control_led.c
> +++ b/sound/core/control_led.c
> @@ -458,11 +458,19 @@ static char *find_eos(char *s)
>
> static char *parse_uint(char *s, unsigned int *val)
> {
> - unsigned long long res;
> - if (kstrtoull(s, 10, &res))
> - res = 0;
> - *val = res;
> - return find_eos(s);
> + char *end = s;
> + char delimiter;
> +
> + while (*end && *end != ',')
> + end++;
> +
> + delimiter = *end;
> + *end = '\0';
> + if (kstrtouint(s, 10, val))
> + *val = 0;
> + *end = delimiter;
> +
> + return delimiter ? end + 1 : end;
> }
>
> static char *parse_string(char *s, char *val, size_t val_size)
prev parent reply other threads:[~2026-11-08 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:45 [PATCH] " Sreeraj S Kurup
2026-11-06 16:23 ` [PATCH v2] " Sreeraj S Kurup
2026-11-08 9:54 ` Sreeraj S Kurup
2026-11-08 10:44 ` Takashi Iwai
2026-11-08 11:18 ` Sreeraj S Kurup
2026-11-08 12:06 ` Takashi Iwai
2026-11-08 12:47 ` Sreeraj S Kurup
2026-11-08 12:48 ` [PATCH v3] " Sreeraj S Kurup
2026-11-08 16:48 ` Manuel Ebner [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=eb3ce9e09ea5f06c427247e8c93e6e1649ac77ba.camel@mailbox.org \
--to=manuelebnerli@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sreekuttan2156239@gmail.com \
--cc=tiwai@suse.com \
--cc=tiwai@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
all inboxes | Powered by JetHome®