All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] ping: [PATCH v13] block/raw-posix.c: Make physical devices usable in QEMU under Mac OS X host
Date: Tue, 2 Feb 2016 15:04:50 -0700	[thread overview]
Message-ID: <56B12802.8010208@redhat.com> (raw)
In-Reply-To: <54A3ED84-6284-48A5-AF16-3B2BE27917C6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

On 02/02/2016 02:23 PM, Programmingkid wrote:

>> And why isn't bsd_path usable for that purpose?
> 
> After trying it out, I found out why bsd_path isn't usable for that purpose. It is because the user might try to use a flash drive as the the cdrom. Say a flash drive is set to /dev/disk2s9. If the user issues the monitor command "change ide1-cd0 /dev/disk2s9", this will make "if (strcmp(filename, "/dev/cdrom") == 0)" false and bsd_path would never be set. bsd_path contents would be garbage.
> 
> This would lead to this code not printing the unmounting directions:
> 
> if (strncmp(filename, "/dev/", 5) == 0) {
>            print_unmounting_directions(filename);
>            return -1;
>        }
> 
> It looks keeping filename as an character array is best.

No, keep filename as a const char * pointer.  It's easy to avoid use of
uninitialized memory.  Try this:

const char *filename;
char bsd_path[MAXPATHLEN] = "";
...
if (strncmp("/dev/cdrom"...) {
    bsd_path = ...
}
...
if (strncmp("/dev/"...) {
    print_unmounting_directions(*bsd_path ? bsd_path : filename);

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-02-02 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 17:08 [Qemu-devel] ping: [PATCH v13] block/raw-posix.c: Make physical devices usable in QEMU under Mac OS X host Programmingkid
2016-02-02 17:16 ` Daniel P. Berrange
2016-02-02 17:28   ` Programmingkid
2016-02-02 17:31     ` Daniel P. Berrange
2016-02-02 19:10       ` Programmingkid
2016-02-02 19:24         ` Eric Blake
2016-02-02 19:46           ` Programmingkid
2016-02-02 21:23           ` Programmingkid
2016-02-02 22:04             ` Eric Blake [this message]
2016-02-03  1:15               ` Programmingkid
2016-02-03  2:30                 ` Eric Blake
2016-02-03  4:21                   ` Programmingkid
2016-02-03  4:36                     ` Eric Blake
2016-02-03 15:54                       ` Programmingkid
2016-02-04 20:58                         ` Eric Blake
2016-02-02 19:29     ` Eric Blake
2016-02-03 10:37       ` Kevin Wolf

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=56B12802.8010208@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-block@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.