XIP can call into get_xip_mem concurrently with the same file,offset withAcked-by: Carsten Otte <cotte@xxxxxxxxxx>
create=1. This usually maps down to get_block, which expects the page lock
to prevent such a situation. This causes ext2 to explode for one reason or
another.
Serialise those calls for the moment. For common usages today, I suspect
get_xip_mem rarely is called to create new blocks. In future as XIP
technologies evolve we might need to look at which operations require
scalability, and rework the locking to suit.
Signed-off-by: Nick Piggin <npiggin@xxxxxxx>