summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorNick Piggin <npiggin@suse.de>2008-08-20 23:09:20 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2008-08-21 00:40:32 +0200
commit14bac5acfdb6a40be64acc042c6db73f1a68f6a4 (patch)
tree5148a0440674ef618a5af4e1b549794db9f783c1 /drivers
parentmm: xip fix fault vs sparse page invalidate race (diff)
downloadlinux-14bac5acfdb6a40be64acc042c6db73f1a68f6a4.tar.xz
linux-14bac5acfdb6a40be64acc042c6db73f1a68f6a4.zip
mm: xip/ext2 fix block allocation race
XIP can call into get_xip_mem concurrently with the same file,offset with 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@suse.de> Cc: Jared Hulbert <jaredeh@gmail.com> Acked-by: Carsten Otte <cotte@freenet.de> Cc: Hugh Dickins <hugh@veritas.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions