> > --- linux-next.orig/fs/read_write.c 2011-11-20 22:02:01.000000000 +0800 > > +++ linux-next/fs/read_write.c 2011-11-20 22:02:03.000000000 +0800 > > @@ -47,6 +47,10 @@ static loff_t lseek_execute(struct file > > file->f_pos = offset; > > file->f_version = 0; > > } > > + > > + if (!(file->f_ra.ra_flags & READAHEAD_LSEEK)) > > + file->f_ra.ra_flags |= READAHEAD_LSEEK; > > + > > return offset; > > } > > Confused. How does READAHEAD_LSEEK get cleared again? I thought it's not necessary (at least for this case). But yeah, it's good to clear it to make it more reasonable and avoid unexpected things. And it would be simple to do, in ra_submit(): - ra->ra_flags &= ~READAHEAD_MMAP; + ra->ra_flags &= ~(READAHEAD_MMAP | READAHEAD_LSEEK); Thanks, Fengguang -- 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
