On Wednesday 18 November 2009, Alan Cox wrote: > > There are drivers touching f_pos in ioctl() methods, which is vaguely > > reasonable. There are also driver touching it in their read()/write() > > methods, which has no effect whatsoever. > > osst is the obvious offender. The ioctl ones like mtdchar seem to be > broken but they have their own locking (or lack thereof) in there own > lseek so its an internal proble,. > The other ones I found before giving up are drivers/s390/char/tape_char.c and drivers/sbus/char/flash.c. Arnd <>< -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
