diff options
| author | Dmitry Monakhov <dmonakhov@sw.ru> | 2007-10-16 01:25:02 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-10-16 09:42:55 -0700 |
| commit | 8268f5a7415d914fc855a86aa2284ac819dc6b2e (patch) | |
| tree | 13628a6d3cb31f04472c4cccdc741979ecdf0ad0 /mm | |
| parent | afddba49d18f346e5cc2938b6ed7c512db18ca68 (diff) | |
| download | kernel-crypto-8268f5a7415d914fc855a86aa2284ac819dc6b2e.tar.gz kernel-crypto-8268f5a7415d914fc855a86aa2284ac819dc6b2e.tar.xz kernel-crypto-8268f5a7415d914fc855a86aa2284ac819dc6b2e.zip | |
deny partial write for loop dev fd
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@openvz.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions