Re: zcat: stdin: decompression OK

["Randy.Dunlap" <rdunlap@xenotime.net>]

On Fri, 24 Feb 2006 09:51:34 +0500 Alexander E. Patrakov wrote:

> Alexey Dobriyan wrote:
> > On Wed, Feb 22, 2006 at 10:53:25PM -0800, Randy.Dunlap wrote:
> >> On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> >>> Unfortunately, I lost my .config from the old kernel, so I attempted the
> >>> following:
> >>>
> >>> cd scripts
> >>> make binoffset
> >>> cd ..
> >>> scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
> >>>
> >>> This results in:
> >>>
> >>> zcat: stdin: decompression OK, trailing garbage ignored
> >> No other output?  what $ARCH?
> >> What did the .config file contain?  was it correct?
> >> so is the only problem the zcat warning message?
> >>
> >> I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
> > 
> > Since I can reproduce it, Randy, what version do you use? 1.3.5-r8 here
> > from Gentoo.
> > 
> > At least, we can trivially shut it up.
> 
> I think this would be wrong, because I am able to extract the config 
> without warnings from 2.6.15-mm2 or even vanilla 2.6.16-rc4, but not 
> vmlinuz-2.6.16-rc3-mm1. So something changed in -mm between 2.6.15-mm2 
> and 2.6.16-rc3-mm1 in the way how bzImages are produced.

Alexey,
It's the final zcat that is complaining -- last one in the script:
	(dd ibs="$off" skip=1 count=0 && dd bs=512k) <"$image" 2>/dev/null | \
		zcat >"$TMPFILE"

The 'dd' command begins at the gzip header of the kernel image file,
but it doesn't know where the end of the gzip area is, it just feeds
everything from $off to zcat, and zcat finds more data than it needs/wants.

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