diff options
author | P J P <prasad@redhat.com> | 2013-11-12 15:10:20 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-11-13 12:09:26 +0900 |
commit | df3ef3af503e131f7848652af8be21747fd57419 (patch) | |
tree | 10c1b49f46fe082814593a00b08151d58177e4c0 /fs/pipe.c | |
parent | 65321547c8be5b00427ac8de23fd15801b68de1f (diff) | |
download | linux-stable-df3ef3af503e131f7848652af8be21747fd57419.tar.gz linux-stable-df3ef3af503e131f7848652af8be21747fd57419.tar.bz2 linux-stable-df3ef3af503e131f7848652af8be21747fd57419.zip |
init/do_mounts_rd.c: fix NULL pointer dereference while loading initramfs
Make menuconfig allows one to choose compression format of an initial
ramdisk image. But this choice does not result in duly compressed initial
ramdisk image. Because - $ make install - does not pass on the selected
compression choice to the dracut(8) tool, which creates the initramfs
file. dracut(8) generates the image with the default compression, ie.
gzip(1).
If a user chose any other compression instead of gzip(1), it leads to a
crash due to NULL pointer dereference in crd_load(), caused by a NULL
function pointer returned by the 'decompress_method()' routine. Because
the initramfs image is gzip(1) compressed, whereas the kernel knows only
to decompress the chosen format and not gzip(1).
This patch replaces the crash by an explicit panic() call with an
appropriate error message. This shall prevent the kernel from
eventually panicking in: init/do_mounts.c: mount_block_root() with
-> panic("VFS: Unable to mount root fs on %s", b);
[akpm@linux-foundation.org: mention that the problem is with the ramdisk, don't print known-to-be-NULL value]
Signed-off-by: P J P <prasad@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/pipe.c')
0 files changed, 0 insertions, 0 deletions