> And your last point about risking unexpected disk-io due to an incorrect
> IOCTL, I would say that is a pretty unlikely in practice. First, I do
> parameter checking on what was passed to the IOCTL, and if things don't
> match, no io is done. Second, how likely is it that you a) call ioctl with
> a (disk) block device, b) pass the wrong ioctl, c) pass along enough data
> to pass the checks in the ioctl, and d) pass along a valid pointer to 512
> bytes of data to overwrite something?
e2fsprogs-1.23 on x86 does this.
-ben
-
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/