> 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,. > > I started grepping through the kernel trying to find any instances > of the first case that uses the BKL, but I only found three instances > of the second case and got heavily demotivated by that. osst probably wants to get an && BROKEN -- 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
