Suparna Bhattacharya <[EMAIL PROTECTED]> wrote: > > > > can you spot what is going wrong here that we have to try and > > > workaround this later ? > > > > Good question. Do we have the i_sem coverage to prevent a concurrent > > truncate? > > > > But from Sebastien's description it doesn't soound as if a concurrent > > truncate is involved. > > Daniel McNeil has a testcase that reproduces the problem - seemed > like a single thread thing - that's what puzzles me.
OK. It'd be nice if we could find a solution which gets around that i_size access in the ISR, if someone has the time to look into it? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
