On Mon 20-09-10 21:40:55, Alexander E. Patrakov wrote: > [I know nothing about linux filesystem code, please disregard this > mail if it is stupid] > > 20.09.2010 21:18, Jan Kara wrote: > > >BKL isn't needed for isofs at all so we can just remove it. Generally, since > >isofs is always mounted read-only, filesystem structure cannot change under us. > > Does your statement also cover the case of read errors on scratched > CD-ROMs (i.e., the driver has successfully read a sector with a > directory once after a lot of strugging, and failed the next time), > or ejects of mounted media? Well, BKL definitely won't help in protecting races triggered by such problems. Also if we fail to read some data, we just bail out with error so data appearing later do not bother us. Similarly once we get hold of some buffer with data, it cannot disappear under us while we hold a reference to it so again we are safe... I don't think these case pose any problem. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- 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
