diff options
| author | Johannes Stezenbach <js@sig21.net> | 2011-06-29 16:25:17 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2011-07-05 11:23:29 +0200 |
| commit | 343f85685ce3f9613c13e4d0f884698194b6a4f6 (patch) | |
| tree | 4f2eb6addc2c333eec2469782c4d1a9f8e355db2 /bt-vhci.c | |
| parent | 661a0f712b7c5b78408d85ba8b7f47ce44f395c0 (diff) | |
| download | qemu-343f85685ce3f9613c13e4d0f884698194b6a4f6.zip qemu-343f85685ce3f9613c13e4d0f884698194b6a4f6.tar.gz qemu-343f85685ce3f9613c13e4d0f884698194b6a4f6.tar.bz2 | |
block/raw-posix: Linux compat-ioctl warning workaround
On Linux x86_64 host with 32bit userspace, running
qemu or even just "qemu-img create -f qcow2 some.img 1G"
causes a kernel warning:
ioctl32(qemu-img:5296): Unknown cmd fd(3) cmd(00005326){t:'S';sz:0} arg(7fffffff) on some.img
ioctl32(qemu-img:5296): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(fff77350) on some.img
ioctl 00005326 is CDROM_DRIVE_STATUS,
ioctl 801c0204 is FDGETPRM.
The warning appears because the Linux compat-ioctl handler for these
ioctls only applies to block devices, while qemu also uses the ioctls on
plain files. Work around by calling fstat() the ensure the ioctls are
only used on block devices.
Signed-off-by: Johannes Stezenbach <js@sig21.net>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'bt-vhci.c')
0 files changed, 0 insertions, 0 deletions