From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: public@hansmi.ch
Subject: Re: [Qemu-devel] [PATCH for-3.1 v3 1/2] usb-mtp: fix utf16_to_str
Date: Mon, 3 Dec 2018 17:11:48 +0100 [thread overview]
Message-ID: <442f3c99-0dd8-f866-5587-b475cf1072eb@redhat.com> (raw)
In-Reply-To: <20181203101045.27976-2-kraxel@redhat.com>
On 3/12/18 11:10, Gerd Hoffmann wrote:
> Make utf16_to_str return an allocated string. Remove the assumtion that
> the number of string bytes equals the number of utf16 chars (which is
> only true for ascii chars). Instead call wcstombs twice, once to figure
> the storage size and once for the actual conversion (as suggested by the
> wcstombs manpage).
>
> Reported-by: Michael Hanselmann <public@hansmi.ch>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> hw/usb/dev-mtp.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/hw/usb/dev-mtp.c b/hw/usb/dev-mtp.c
> index 00a3691bae..0f6a9702ef 100644
> --- a/hw/usb/dev-mtp.c
> +++ b/hw/usb/dev-mtp.c
> @@ -1593,17 +1593,23 @@ static void usb_mtp_cancel_packet(USBDevice *dev, USBPacket *p)
> fprintf(stderr, "%s\n", __func__);
> }
>
> -static void utf16_to_str(uint8_t len, uint16_t *arr, char *name)
> +static char *utf16_to_str(uint8_t len, uint16_t *arr)
> {
> - int count;
> - wchar_t *wstr = g_new0(wchar_t, len);
> + wchar_t *wstr = g_new0(wchar_t, len + 1);
> + int count, dlen;
> + char *dest;
>
> for (count = 0; count < len; count++) {
> + /* FIXME: not working for surrogate pairs */
> wstr[count] = (wchar_t)arr[count];
> }
> + wstr[count] = 0;
>
> - wcstombs(name, wstr, len);
> + dlen = wcstombs(NULL, wstr, 0) + 1;
> + dest = g_malloc(dlen);
> + wcstombs(dest, wstr, dlen);
> g_free(wstr);
> + return dest;
> }
>
> /* Wrapper around write, returns 0 on failure */
> @@ -1703,7 +1709,7 @@ static void usb_mtp_write_metadata(MTPState *s)
> {
> MTPData *d = s->data_out;
> ObjectInfo *dataset = (ObjectInfo *)d->data;
> - char *filename = g_new0(char, dataset->length);
> + char *filename;
> MTPObject *o;
> MTPObject *p = usb_mtp_object_lookup(s, s->dataset.parent_handle);
> uint32_t next_handle = s->next_handle;
> @@ -1711,7 +1717,7 @@ static void usb_mtp_write_metadata(MTPState *s)
> assert(!s->write_pending);
> assert(p != NULL);
>
> - utf16_to_str(dataset->length, dataset->filename, filename);
> + filename = utf16_to_str(dataset->length, dataset->filename);
>
> o = usb_mtp_object_lookup_name(p, filename, dataset->length);
> if (o != NULL) {
>
next prev parent reply other threads:[~2018-12-03 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 10:10 [Qemu-devel] [PATCH for-3.1 v3 0/2] usb-mtp: two bugfixes (one security fix) Gerd Hoffmann
2018-12-03 10:10 ` [Qemu-devel] [PATCH for-3.1 v3 1/2] usb-mtp: fix utf16_to_str Gerd Hoffmann
2018-12-03 14:59 ` Peter Maydell
2018-12-03 16:11 ` Philippe Mathieu-Daudé [this message]
2018-12-03 18:10 ` Markus Armbruster
2018-12-03 10:10 ` [Qemu-devel] [PATCH for-3.1 v3 2/2] usb-mtp: outlaw slashes in filenames Gerd Hoffmann
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=442f3c99-0dd8-f866-5587-b475cf1072eb@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=public@hansmi.ch \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).