summaryrefslogtreecommitdiff
path: root/Documentation/io_ordering.txt
diff options
context:
space:
mode:
authorYinghai Lu <yinghai@kernel.org>2014-08-08 21:23:12 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2014-08-08 22:57:26 (GMT)
commit38747439914c468ecba70b492b54dc4ef0b50453 (patch)
treedbb80c9d8c7be76a8a0483c5ec7a271361162429 /Documentation/io_ordering.txt
parent4d4b866aee039d609c0b40e7e5b27204607ce614 (diff)
downloadlinux-38747439914c468ecba70b492b54dc4ef0b50453.tar.xz
initramfs: support initrd that is bigger than 2GiB
When initrd (compressed or not) is used, kernel report data corrupted with /dev/ram0. The root cause: During initramfs checking, if it is initrd, it will be transferred to /initrd.image with sys_write. sys_write only support 2G-4K write, so if the initrd ram is more than that, /initrd.image will not complete at all. Add local xwrite to loop calling sys_write to workaround the problem. Also need to use xwrite in write_buffer() to handle: image is uncompressed cpio and there is one big file (>2G) in it. unpack_to_rootfs ===> write_buffer ===> actions[]/do_copy At the same time, we don't need to worry about sys_read/sys_write in do_mounts_rd.c::crd_load. As decompressor will have fill/flush and local buffer that is smaller than 2G. Test with uncompressed initrd, and compressed ones with gz, bz2, lzma,xz, lzop. Signed-off-by: Yinghai Lu <yinghai@kernel.org> Acked-by: H. Peter Anvin <hpa@zytor.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> Cc: "Daniel M. Weeks" <dan@danweeks.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/io_ordering.txt')
0 files changed, 0 insertions, 0 deletions