mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: dhammika <dpathirana@sri.receiptcity.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: understanding gunzip
Date: Mon, 08 Jan 2001 09:36:34 -0600	[thread overview]
Message-ID: <3A59DE82.2A175A3@sri.receiptcity.com> (raw)

hi,

i tried 2.4.0 kernel with rmk and np patches in my brutus board. (Brutus
is a StrongArm based development environment)

my patched kernel is 2.4.0-rmk1-np1

the kernel uncompresses fine. but uncompressing the ramdisk fails. In
this  instance my uncompressed ramdisk is about 3.5mb.

i looked in to gunzip() routine. in inflate() (inflate.c)
i found following,

  do {
    hufts = 0;
    gzip_mark(&ptr);
    if ((r = inflate_block(&e)) != 0) {
      gzip_release(&ptr);
      return r;
    }
    gzip_release(&ptr);
    if (hufts > h)
      h = hufts;
  } while (!e);

and gzip_mark() and gzip_release() are defined in rd.c as,

static void __init gzip_mark(void **ptr)
{
}

static void __init gzip_release(void **ptr)
{
}

now if i comment these gzip_mark and gzip_release lines then the kernel
would complain,

Out of memory

 -- System halted

then i tried to see where ptr is poinitng to, according to the
System.map it points to a variable called insize,

it's defined as

./arch/arm/boot/compressed/misc.c     :     static unsigned insize = 0;
/* valid bytes in inbuf */

i don't understand what is happening here!! or did i miss anything??

tia

dhammika




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2001-01-08  3:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3A59DE82.2A175A3@sri.receiptcity.com \
    --to=dpathirana@sri.receiptcity.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®