search for: ioctl's

...67611 blazer_usb CALL chdir(0x40e1bc) 67611 blazer_usb NAMI "/var/db/nut" 67611 blazer_usb RET chdir 0 67611 blazer_usb CALL open(0x8008383a1,0<O_RDONLY>,<unused>0) 67611 blazer_usb NAMI "/dev/usbctl" 67611 blazer_usb RET open 4 67611 blazer_usb CALL ioctl(0x4,USB_READ_DIR,0x7fffffffca60) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL open(0x7fffffffcba0,0x2<O_RDWR>,<unused>0) 67611 blazer_usb NAMI "/dev/ugen0.1" 67611 blazer_usb RET open 5 67611 blazer_usb CALL ioctl(0x5,USB_GET_PLUGTIME,0x7fffffffcc0c) 67611 b...

From: Asahi Lina <lina at asahilina.net> DRM drivers need to be able to declare which driver-specific ioctls they support. Add an abstraction implementing the required types and a helper macro to generate the ioctl definition inside the DRM driver. Note that this macro is not usable until further bits of the abstraction are in place (but it will not fail to compile on its own, if not called). Signed-of...

...ru UPS connected by USB using nutdrv_qx driver. As I see that it was using too much CPU time (or at least, too much for what I think it should be normal), I used strace to see what is was using, and got a lot of lines like these: %<------------%<------------%<------------%<------------ ioctl(4, USBDEVFS_REAPURBNDELAY, 0x7ffdca143278) = -1 EAGAIN (Resource temporarily unavailable) select(5, NULL, [4], NULL, {0, 1000}) = 0 (Timeout) ioctl(4, USBDEVFS_REAPURBNDELAY, 0x7ffdca143278) = -1 EAGAIN (Resource temporarily unavailable) select(5, NULL, [4], NULL, {0, 1000}) = 0 (Timeout) ioctl...

...t with all this stuff, having in mind that I don't want to learn all the HID stuff - just some basics (probably just an example) necessary to implement the driver. (*) their program is looping doing the following at regular intervals: 654 time(NULL) = 1200921228 654 ioctl(3, HIDIOCGUSAGE, {report_type=1, report_id=0, field_index=0, usage_index=0, usage_code=ffa00001, value=240}) = 0 654 select(4, [3], NULL, NULL, {3, 0}) = 1 (in [3], left {2, 990000}) 654 read(3, "\1\0\240\377\360\0\0\0\1\0\240\377\0\0\0\0\1\0\240\377\0\0\0\0\1\0\240\377\0\0\0\0\1\0\240\377...

...of doing a large zfs send | zfs receive when I decided that I wanted to terminate the the zfs send process. I killed it, but the zfs receive doesn''t want to die... In the meantime my zfs list command just hangs. Here is the tail end of the truss output from a "truss zfs list": ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08043484) = 0 ioctl(3, ZFS_IOC_SNAPSHOT_LIST_NEXT, 0x08045788) Err#3 ESRCH ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08046950) = 0 ioctl(3, ZFS_IOC_OBJSET_STATS, 0x0804464C) = 0 ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08045788) Err#3 ESRCH ioctl(3, ZFS_IOC_SNAPSHOT_LI...

Hey all -- First post, so first off thanks for creating this wonderful software and helping out new users like me adapt to the wine-way :) Has anyone managed to get Windows/Mac only data analysis and vis suite Tableau Public (http://www.tableausoftware.com/public/download) running with any version Wine yet? It goes through the motions of installing, but then won't run. I'd welcome any

...ab.c:3553 [<0000000079ebab38>] kmalloc include/linux/slab.h:547 [inline] [<0000000079ebab38>] vhost_net_ubuf_alloc drivers/vhost/net.c:241 [inline] [<0000000079ebab38>] vhost_net_set_backend drivers/vhost/net.c:1534 [inline] [<0000000079ebab38>] vhost_net_ioctl+0xb43/0xc10 drivers/vhost/net.c:1716 [<000000009f6204a2>] vfs_ioctl fs/ioctl.c:46 [inline] [<000000009f6204a2>] file_ioctl fs/ioctl.c:509 [inline] [<000000009f6204a2>] do_vfs_ioctl+0x62a/0x810 fs/ioctl.c:696 [<00000000b45866de>] ksys_ioctl+0x86/0xb0 fs/io...

...ab.c:3553 [<0000000079ebab38>] kmalloc include/linux/slab.h:547 [inline] [<0000000079ebab38>] vhost_net_ubuf_alloc drivers/vhost/net.c:241 [inline] [<0000000079ebab38>] vhost_net_set_backend drivers/vhost/net.c:1534 [inline] [<0000000079ebab38>] vhost_net_ioctl+0xb43/0xc10 drivers/vhost/net.c:1716 [<000000009f6204a2>] vfs_ioctl fs/ioctl.c:46 [inline] [<000000009f6204a2>] file_ioctl fs/ioctl.c:509 [inline] [<000000009f6204a2>] do_vfs_ioctl+0x62a/0x810 fs/ioctl.c:696 [<00000000b45866de>] ksys_ioctl+0x86/0xb0 fs/io...

...srpm from http://xenbits.xensource.com/kernels/rhel3x/kernel-2.4.21-47.0.1.EL.xs0.3.5. 15.src.rpm (I get the same issue using the binary RPM) the dom0 is running 3.0.3_0 Upon booting the DomU, (the DomU has been passed phy:/dev/sda6, which has been partitioned using qemu) I get the following ioctl errors. ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported by XL blkif relivant bit from dmesg follows: Freeing...

...ee, 0, len, GFP_NOFS); if (ordered) btrfs_put_ordered_extent(ordered); btrfs_wait_ordered_range(inode, 0, len); } with btrfs_wait_ordered_range(inode, 0, (u64)-1); - return the uncompressed size on disk for uncompressed filesystems instead of EINVAL Minimal example: #include <sys/ioctl.h> #include <fcntl.h> #include <stdint.h> #include <stdio.h> #define BTRFS_IOCTL_MAGIC 0x94 #define BTRFS_IOC_COMPR_SIZE _IOR(BTRFS_IOCTL_MAGIC, 21, uint64_t) int main(int argc, char **argv) { uint64_t size = -1; int d = open(argv[1], O_RDONLY); ioctl(d, BTRFS_IOC_...

...e. Thus, be +prepared that we keep breaking your userspace application and guest +compatibility over and over again until we feel happy with the result. Make sure +your guest kernel, your host kernel, and your userspace launcher are in a +consistent state. + +This Documentation describes the unique ioctl calls to /dev/kvm, the resulting +kvm-vm file descriptors, and the kvm-vcpu file descriptors that differ from x86. + +1. ioctl calls to /dev/kvm +KVM does support the following ioctls on s390 that are common with other +architectures and do behave the same: +KVM_GET_API_VERSION +KVM_CREATE_VM (*)...

...e. Thus, be +prepared that we keep breaking your userspace application and guest +compatibility over and over again until we feel happy with the result. Make sure +your guest kernel, your host kernel, and your userspace launcher are in a +consistent state. + +This Documentation describes the unique ioctl calls to /dev/kvm, the resulting +kvm-vm file descriptors, and the kvm-vcpu file descriptors that differ from x86. + +1. ioctl calls to /dev/kvm +KVM does support the following ioctls on s390 that are common with other +architectures and do behave the same: +KVM_GET_API_VERSION +KVM_CREATE_VM (*)...

Hi everyone, This patchset is the latest approach I''m using for the Ceph storage daemon to keep track of which data has safely committed to disk. The basic idea is to not use the (problematic) user transaction ioctls at all. Instead, the daemon quiesces its own write requests, initiates an async snapshot, and then continues. The snapshot approach is nice because it provides rollback. If something goes wrong, we can cleanly go back to the most recent consistent commit. The performance is also very similar t...

...; err:ole:CoGetClassObject no class object {275c23e2-3747-11d0-9fea-00aa003f8646} could be created for context 0x3 fixme:bitblt:X11DRV_ClientSideDIBCopy potential optimization: client-side complex region clipping fixme:wtsapi:WTSRegisterSessionNotification Stub 0x400bc 0x00000000 fixme:ntdll:server_ioctl_file Unsupported ioctl 70c00 (device=7 access=0 func=300 method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl 70c00 (device=7 access=0 func=300 method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl 70c00 (device=7 access=0 func=300 method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl...

...__u64 u64; > > > > > > struct vhost_vring_state state; > > > > > > struct vhost_vring_addr addr; > > > > > > } payload; > > > > > > }; > > > > > > > > > > > > The existing vhost-kernel ioctl cmds are reused as the message > > > > > > requests in above structure. > > > > > Still a comments like V1. What's the advantage of inventing a new protocol? > > > > I'm trying to make it work in VFIO's way.. > > > > > > &g...

...__u64 u64; > > > > > > struct vhost_vring_state state; > > > > > > struct vhost_vring_addr addr; > > > > > > } payload; > > > > > > }; > > > > > > > > > > > > The existing vhost-kernel ioctl cmds are reused as the message > > > > > > requests in above structure. > > > > > Still a comments like V1. What's the advantage of inventing a new protocol? > > > > I'm trying to make it work in VFIO's way.. > > > > > > &g...

...OCK|O_DIRECTORY) = 4 fstat(4, {st_mode=S_IFDIR|0755, st_size=60, ...}) = 0 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 getdents(4, /* 3 entries */, 4096) = 72 open("/dev/bus/usb/001/001", O_RDWR) = -1 EACCES (Permission denied) open("/dev/bus/usb/001/001", O_RDONLY) = 5 ioctl(5, USBDEVFS_CONNECTINFO, 0x7fff23b761b0) = -1 EPERM (Operation not permitted) read(5, "\22\1\20\1\t\0\0@\0\0\0\0\6\2\3\2\1\1", 18) = 18 read(5, "\t\2\31\0\1\1\0\340", 8) = 8 read(5, "\0\t\4\0\0\1\t\0\0\0\7\5\201\3\2\0\377", 17) = 17 close(5)...

Hi Ben, Karol and Tom are seeing this on init with a nvif-enabled kernel + libdrm. What are we doing wrong? I think that route == NVIF_IOCTL_V0_ROUTE_NVIF (== 0), while owner is apparently 1, whatever that is. [362619.242238] nouveau: glxgears[6096]:00000000:00000000: ioctl: size 32 [362619.242240] nouveau: glxgears[6096]:00000000:00000000: ioctl: vers 0 type 00 object 0000000000000000 owner 00 [362619.242241] nouveau: glxgears[6096]:0...

...> > > > > struct vhost_vring_addr addr; > > > > > > > > > > } payload; > > > > > > > > > > }; > > > > > > > > > > > > > > > > > > > > The existing vhost-kernel ioctl cmds are reused as the message > > > > > > > > > > requests in above structure. > > > > > > > > > Still a comments like V1. What's the advantage of inventing a new protocol? > > > > > > > > I'm trying to make i...

...> > > > > struct vhost_vring_addr addr; > > > > > > > > > > } payload; > > > > > > > > > > }; > > > > > > > > > > > > > > > > > > > > The existing vhost-kernel ioctl cmds are reused as the message > > > > > > > > > > requests in above structure. > > > > > > > > > Still a comments like V1. What's the advantage of inventing a new protocol? > > > > > > > > I'm trying to make i...