On Sat, Nov 19, 2011 at 05:32:05PM +0800, Yongqiang Yang wrote: > Currently, we clear revoked flag only when a block is reused. However, > this can tigger a false journal error. Consider a situation when a block > is used as a meta block and is deleted(revoked) in ordered mode, then the > block is allocated as a data block to a file. At this moment, user changes > the file's journal mode from ordered to journaled and truncates the file. > The block will be considered re-revoked by journal because it has revoked > flag still pending from the last transaction and an assertion triggers. > > We fix the problem by keeping the revoked status more uptodate - we clear > revoked flag when switching revoke tables to reflect there is no revoked > buffers in current transaction any more. > > Signed-off-by: Yongqiang Yang <xiaoqiangnk@xxxxxxxxx> Oops, I replied the wrong message. This is the version of the patch which I applied... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
