Hugh Dickins: > It certainly shouldn't be. The problem would have come from two > racing i_size_write(dst)s, one of the unlocked increments getting > lost, leaving seqcount odd, so the next i_size_read(dst) would > spin forever waiting for it to go even. I see. The unlocked increment can cause the next i_size_read() hang. > I'm not sure what you mean by that. i_size_read() doesn't fail, > but it may loop; and if the seqcount has got out of step from > concurrent unlocked i_size_write()s, then it'll spin forever. What I meant by "fail" was "loop" actually. And I understand that you didn't writing directly (bypassing unionfs) too. Junjiro Okajima -- 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
