public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: Rob Landley <rob@landley.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Fix NULL pointer dereference while loading initramfs
Date: Wed, 25 Sep 2013 00:31:51 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.2.03.1309250016290.5312@erqung.pbz> (raw)
In-Reply-To: <1379986687.1974.63@driftwood>

  Hello Rob,

+-- On Mon, 23 Sep 2013, Rob Landley wrote --+
| I've been building kernels, including with initramfs, and I don't have
| dracut(8) installed? In today's git:

  dracut(8) is a separate tool installed from package dracut.

 -> dracut-029-2.fc19.x86_64
 -> https://dracut.wiki.kernel.org/

 
| I've been messing with this area and maight be interested if I had any idea 
| what this guy was talking about?

  Kernel menuconfig selects gzip(1) as a default compression format for the 
initial ramdisk image.

  $ make menuconfig
   -> General setup
    -> Support initial ramdisk compressed using ...

If instead of gzip(1), you select bzip2(1) or xz(1) format and build a new 
kernel, the initramfs image would still be compressed with gzip(1), because 
currently there is no way to pass the selected compression format to dracut(8) 
via $ make install.

# file /boot/initramfs-3.11.0.img 
/boot/initramfs-3.11.0.img: LZMA compressed data, streamed

It shows LZMA because I've patched /sbin/new-kernel-pkg to use 
$INITRD_COMPRESS variable.

Thank you.
--
Prasad J Pandit / Red Hat Security Response Team
DB7A 84C5 D3F9 7CD1 B5EB  C939 D048 7860 3655 602B

  reply	other threads:[~2013-09-24 19:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-15  9:03 [PATCH 1/2] Fix NULL pointer dereference while loading initramfs P J P
2013-09-23 19:41 ` Andrew Morton
2013-09-24  1:38   ` Rob Landley
2013-09-24 19:01     ` P J P [this message]
2013-09-24 18:45   ` P J P
2013-09-30 21:43   ` P J P
2013-10-05 20:42   ` P J P
2013-10-05 21:28     ` Andrew Morton
2013-10-06  8:09       ` P J P

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.03.1309250016290.5312@erqung.pbz \
    --to=ppandit@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox