The patch titled
deny partial write for loop dev fd
has been added to the -mm tree. Its filename is
deny-partial-write-for-loop-dev-fd.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: deny partial write for loop dev fd
From: Dmitry Monakhov <dmonakhov@xxxxx>
Partial write can be easily supported by LO_CRYPT_NONE mode, but it is not
easy in LO_CRYPT_CRYPTOAPI case, because of its block nature. I don't know
who still used cryptoapi, but theoretically it is possible. So let's leave
things as they are. Loop device doesn't support partial write before
Nick's "write_begin/write_end" patch set, and let's it behave the same way
after.
Signed-off-by: Dmitriy Monakhov <dmonakhov@xxxxxxxxxx>
Cc: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/block/loop.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff -puN drivers/block/loop.c~deny-partial-write-for-loop-dev-fd drivers/block/loop.c
--- a/drivers/block/loop.c~deny-partial-write-for-loop-dev-fd
+++ a/drivers/block/loop.c
@@ -244,10 +244,8 @@ static int do_lo_send_aops(struct loop_d
ret = pagecache_write_end(file, mapping, pos, size, copied,
page, fsdata);
- if (ret < 0)
+ if (ret < 0 || ret != copied)
goto fail;
- if (ret < copied)
- copied = ret;
if (unlikely(transfer_result))
goto fail;
_
Patches currently in -mm which might be from dmonakhov@xxxxx are
mspec_mmap-dont-set-vm_locked.patch
fs-introduce-write_begin-write_end-and-perform_write-aops.patch
deny-partial-write-for-loop-dev-fd.patch
ext3-convert-to-new-aops-fix.patch
ext4-convert-to-new-aops-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
