From: Eric Blake <eblake@redhat.com>
To: Dimitris Aragiorgis <dimara@arrikto.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 5/5] raw-posix: Introduce hdev_is_sg()
Date: Thu, 18 Jun 2015 14:16:43 -0600 [thread overview]
Message-ID: <5583272B.2010600@redhat.com> (raw)
In-Reply-To: <1432115859-11413-6-git-send-email-dimara@arrikto.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On 05/20/2015 03:57 AM, Dimitris Aragiorgis wrote:
> Until now, an SG device was identified only by checking if its path
> started with "/dev/sg". Then, hdev_open() set bs->sg accordingly.
> This is very fragile, e.g. it fails with symlinks or relative paths.
> We should rely on the actual properties of the device instead of the
> specified file path.
>
> Test for an SG device (e.g. /dev/sg0) by ensuring that all of the
> following holds:
>
> - The device supports the SG_GET_VERSION_NUM ioctl
> - The device supports the SG_GET_SCSI_ID ioctl
> - The specified file name corresponds to a character device
I'd check stat first. ioctl's on the wrong device type might have
unexpected side effects.
> +static int hdev_is_sg(BlockDriverState *bs)
> +{
> +
> +#if defined(__linux__)
> +
> + struct stat st;
> + struct sg_scsi_id scsiid;
> + int sg_version;
> +
> + if (!bdrv_ioctl(bs, SG_GET_VERSION_NUM, &sg_version) &&
> + !bdrv_ioctl(bs, SG_GET_SCSI_ID, &scsiid) &&
> + stat(bs->filename, &st) >= 0 && S_ISCHR(st.st_mode)) {
> + DPRINTF("SG device found: type=%d, version=%d\n",
> + scsiid.scsi_type, sg_version);
> + return 1;
> + }
> +
> +#endif
> +
> + return 0;
Make this return 'bool', using 'true' and 'false'. We require a C99
compiler, after all.
--
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 --]
next prev parent reply other threads:[~2015-06-18 20:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 9:57 [Qemu-devel] [PATCH v4 0/5] Some fixes related to scsi-generic Dimitris Aragiorgis
2015-05-20 9:57 ` [Qemu-devel] [PATCH v4 1/5] block: Use bdrv_is_sg() everywhere Dimitris Aragiorgis
2015-06-19 12:18 ` Stefan Hajnoczi
2015-05-20 9:57 ` [Qemu-devel] [PATCH v4 2/5] Fix migration in case of scsi-generic Dimitris Aragiorgis
2015-06-19 12:23 ` Stefan Hajnoczi
2015-05-20 9:57 ` [Qemu-devel] [PATCH v4 3/5] raw-posix: DPRINTF instead of DEBUG_BLOCK_PRINT Dimitris Aragiorgis
2015-06-18 20:05 ` Eric Blake
2015-06-19 12:25 ` Stefan Hajnoczi
2015-05-20 9:57 ` [Qemu-devel] [PATCH v4 4/5] raw-posix: Use DPRINTF for DEBUG_FLOPPY Dimitris Aragiorgis
2015-06-18 20:14 ` Eric Blake
2015-06-19 12:25 ` Stefan Hajnoczi
2015-05-20 9:57 ` [Qemu-devel] [PATCH v4 5/5] raw-posix: Introduce hdev_is_sg() Dimitris Aragiorgis
2015-06-18 20:16 ` Eric Blake [this message]
2015-06-19 12:33 ` Stefan Hajnoczi
2015-06-22 10:18 ` Dimitris Aragiorgis
2015-06-22 12:33 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-05-29 5:15 ` [Qemu-devel] [PATCH v4 0/5] Some fixes related to scsi-generic Dimitris Aragiorgis
2015-06-18 11:07 ` Dimitris Aragiorgis
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=5583272B.2010600@redhat.com \
--to=eblake@redhat.com \
--cc=dimara@arrikto.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).