lkml.org 
[lkml]   [2007]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: ioctl32: Unknown cmd
    Date
    On Tuesday 16 October 2007, Geert Uytterhoeven wrote:
    > The recent (post 2.6.23) changes to compat_ioctl made the reporting of
    > unsupported ioctls more verbose. E.g. on the PS3 I get:
    >
    > | ioctl32(cdrom_id:608): Unknown cmd fd(3) cmd(00005331){t:'S';sz:0} arg(00000000) on /dev/.tmp-11-0
    > | ioctl32(hdparm:1427): Unknown cmd fd(3) cmd(0000031f){t:03;sz:0} arg(00000000) on /dev/ps3da
    > | ioctl32(hdparm:1427): Unknown cmd fd(3) cmd(0000031f){t:03;sz:0} arg(00000000) on /dev/ps3da
    >
    > The first one is triggered by the detection of the CD/DVD/BD-ROM driver,
    > The others are triggered by me running hdparm.
    >
    > Was this intentional?
    >

    No, it was certainly not intentional, and I can't figure out why it happens.
    The ioctl numbers from your example are HDIO_DRIVE_CMD and CDROM_GET_CAPABILITY,
    both of which should be handled through compat_blkdev_driver_ioctl by calling
    the native ioctl method of the driver, and return -ENOTTY otherwise.

    The one point where it is expected to have changed now is when you try
    to do these ioctls on something that is not a block device. Are you sure that
    the files you tried them on were created correctly?

    Arnd <><
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-10-16 21:53    [W:0.020 / U:1.768 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site