linux-kernel - Re: HDIO_DRIVE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070510124145.GA19856@infradead.org>
Date:	Thu, 10 May 2007 13:41:45 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: HDIO_DRIVE_CMD and hdparm

On Thu, May 10, 2007 at 02:12:59PM +0200, Geert Uytterhoeven wrote:
> 	Hi,
> 
> `hdparm -t' uses HDIO_DRIVE_CMD(null) to flush the disk's buffer.
> When using it on my own block device (the new PS3 disk storage driver), hdparm
> gives the following error message:
> 
> | HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
> 
> When using it on an ATA or SCSI device, no such error message is printed.
> 
> According to the hdparm sources, hdparm expects the HDIO_DRIVE_CMD(null) ioctl
> to either succeed, or to fail with errno EINVAL.
> 
> Apparently handling of ioctls is different for the different device types:
>   - ATA/SATA handle HDIO_DRIVE_CMD(null) (and a few other variants)
>     => fine for hdparm
>   - SCSI doesn't handle HDIO_DRIVE_CMD(null), and returns EINVAL
>     => fine for hdparm
>   - If a block device doesn't support the ioctl, blkdev_driver_ioctl() returns
>     ENOTTY
>     => hdparm error message
> 
> Which one is correct?
>   - blkdev_ioctl()/blkdev_driver_ioctl() return -ENOTTY
>   - scsi_cmd_ioctl() returns -ENOTTY
>   - scsi_ioctl() returns -EINVAL
>   - cdrom_ioctl() returns -ENOSYS to mean not handled, continue
>   - some block layer routines return -ENOIOCTLCMD to mean not handled, continue

ENOTTY is the traditional unix errno value for this ioctl is not implemented.
ENOIOCTLCMD is a new fashioned code meaning about the same.  In the block
layer the latter should be used as generic code should handlde this.

> 
> My questions:
>   1. Does any of these have to be fixed?
>   2. Shall I add a dummy HDIO_DRIVE_CMD(null) handler to my block device to
>      return -EINVAL?
>   3. Shall I just ignore the hdparm error message?

I suspect you can just ignore this.  Even better send a patch to the hdparm
maintainer to deal with ENOTTY aswell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/