On Wed, 16 Jan 2008, Oliver Neukum wrote: > > The only scenario where this would matter is when there are two > > overlapping open calls, of which one uses ioctls and the other does > > doesn't. I can't think of any examples, except perhaps where somebody > > does an ioctl on a mounted device (note that mounting a device does an > > Exactly. In fact strictly speaking you must do it this way, or you have no > guarantee that you mount what you did an ioctl() on.
I didn't express myself clearly. I meant that the device holds a mounted filesystem at the time some user task opens the block device file, does an ioctl on it, and then closes it. The effect of the ioctl would persist as long as the filesystem was mounted. Maybe that's the desired behavior. Certainly it's not recommended to do an ioctl on a device that's already mounted. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
