alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
	mengdong.lin@intel.com, broonie@kernel.org,
	rakesh.a.ughreja@intel.com, liam.r.girdwood@intel.com,
	hardik.t.shah@intel.com, subhransu.s.prusty@intel.com
Subject: Re: [PATCH v2 6/7] topology: Add support for parsing vendor tuples
Date: Tue, 5 Apr 2016 16:53:24 +0800	[thread overview]
Message-ID: <57037D04.20604@linux.intel.com> (raw)
In-Reply-To: <s5hegakzinu.wl-tiwai@suse.de>


On 04/05/2016 02:14 PM, Takashi Iwai wrote:
> On Tue, 05 Apr 2016 07:47:08 +0200,
> Mengdong Lin wrote:
>>
>>
>>
>> On 03/30/2016 03:35 PM, Takashi Iwai wrote:
>>> On Wed, 30 Mar 2016 09:11:17 +0200,
>>> mengdong.lin@linux.intel.com wrote:
>>>>
>>>> +		switch (type) {
>>>> +		case SND_SOC_TPLG_TUPLE_TYPE_UUID:
>>>> +			len = strlen(value);
>>>> +			if (len > 16 || len == 0) {
>>>> +				SNDERR("error: tuple %s: invalid uuid\n", id);
>>>> +				goto err;
>>>> +			}
>>>> +
>>>> +			memcpy(tuple->uuid, value, 16);
>>>
>>> This may still overflow :)
>>> How about simply using elem_copy_text()?
>>
>> Sorry for the late reply.
>>
>> Would you mind me using uuid_parse() here?
>> It can convert an input UUID string into the binary representation.
>>
>> An UUID string link "1b4e28ba-2fa1-11d2-883f-b9a761bde3fb" is user
>> friendly for the text conf file. But this will add dependency on libuuid.
>
> Additional dependency is no-go, especially when the required change is
> so trivial.  It's just a string copy, after all.
>

Maybe we can just use strncpy(dest, src, 16), assuming the strncpy will 
not try to write a "\0" at dest[16] that may cause overflow?

The user need to define uuid without "-" in the UUID string in the text 
conf file.

Now the uuid value in ABI is 16-character array:

/* vendor tuple for uuid */
struct snd_soc_tplg_vendor_uuid_elem {
	__le32 token;
	char uuid[16];
} __attribute__((packed));

The last byte of UUID may not be zero.

Thanks
Mengdong

  reply	other threads:[~2016-04-05  8:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:09 [PATCH v2 0/7] topology: Add support for vendor tuples mengdong.lin
2016-03-30  7:10 ` [PATCH v2 1/7] topology: Use the generic pointer to free an element's object mengdong.lin
2016-03-30  7:10 ` [PATCH v2 2/7] topology: Define a free handler for the element mengdong.lin
2016-03-30  7:10 ` [PATCH v2 3/7] topology: Add doc for vendor tuples mengdong.lin
2016-03-30  7:11 ` [PATCH v2 4/7] topology: ABI - Define types " mengdong.lin
2016-03-30  7:11 ` [PATCH v2 5/7] topology: Add support for vendor tokens mengdong.lin
2016-03-30  7:11 ` [PATCH v2 6/7] topology: Add support for parsing vendor tuples mengdong.lin
2016-03-30  7:35   ` Takashi Iwai
2016-04-05  5:47     ` Mengdong Lin
2016-04-05  6:14       ` Takashi Iwai
2016-04-05  8:53         ` Mengdong Lin [this message]
2016-04-05  9:38           ` Takashi Iwai
2016-04-05 15:38             ` Lin, Mengdong
2016-03-30  7:11 ` [PATCH v2 7/7] topology: Build data objects with tuples mengdong.lin

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=57037D04.20604@linux.intel.com \
    --to=mengdong.lin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hardik.t.shah@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=rakesh.a.ughreja@intel.com \
    --cc=subhransu.s.prusty@intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).