On 12-05-04 09:06 AM, Mark Lord wrote: > On 12-05-04 02:39 AM, Paolo Bonzini wrote: >> Il 03/05/2012 19:36, Mark Lord ha scritto: >> >>>>>>> Dunno which flags, I'm just ignoring them and waiting >>>>>>> for the noise message to get reverted. >> >> I said which ioctls, not which options. I.e. cut-and-paste from dmesg. > > Here are some: > > > messages.1:Apr 28 14:08:09 zbox5 kernel: [ 268.800536] hdparm: sending ioctl 330 to a partition! > messages.1:Apr 28 14:08:09 zbox5 kernel: [ 268.800547] hdparm: sending ioctl 330 to a partition! > messages.1:Apr 28 14:08:57 zbox5 kernel: [ 316.413944] hdparm: sending ioctl 330 to a partition! > messages.1:Apr 28 14:08:57 zbox5 kernel: [ 316.413951] hdparm: sending ioctl 330 to a partition! > messages.1:Apr 28 14:20:10 zbox5 kernel: [ 989.525085] hdparm: sending ioctl 330 to a partition! > messages.1:Apr 28 14:20:10 zbox5 kernel: [ 989.525093] hdparm: sending ioctl 330 to a partition! > > The in <linux/hdreg.h> say this about 330: > > ... > /* 0x330 is reserved - used to be HDIO_GETGEO_BIG */ > ... > > So it's HDIO_GETGEO_BIG, which doesn't exist in newer kernels. > I wonder when that got removed? Minor userspace breakage there. Looks like it got removed about 10 years ago, either in 2.5.xx or early 2.6.xx, so that's all fine now. hdparm still issues it for backward compatibility with kernels that lack more modern methods. Currently we don't try to inspect the kernel version at run-time, because version numbers are not as reliable as simply issuing the ioctl(). > hdparm issues it first as a backward-compatibility thing, > before falling back to the even-more obsolete HDIO_GETGEO, > which curiously enough is still in modern kernels. > > Cheers > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
