From: Tom Rini <trini@kernel.crashing.org>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: "Jörn Engel" <joern@logfs.org>,
phillip@lougher.demon.co.uk, linux-fsdevel@vger.kernel.org,
jacmet@sunsite.dk, rpurdie@rpsys.net, linuxppc-dev@ozlabs.org,
chris@zankel.net
Subject: Re: [Patch] NULL pointer deref with corrupted squashfs image
Date: Tue, 20 Jan 2009 11:47:02 -0700 [thread overview]
Message-ID: <20090120184702.GB30203@smtp.west.cox.net> (raw)
In-Reply-To: <20090120163957.GA21339@alice>
On Tue, Jan 20, 2009 at 05:47:14PM +0100, Eric Sesterhenn wrote:
> * Jörn Engel (joern@logfs.org) wrote:
> > On Fri, 16 January 2009 16:07:00 -0700, Tom Rini wrote:
> > >
> > > Sounds like a plan to me, except maybe zlib_inflate_unsafe() and a
> > > comment above the wrapper saying what/why is going on?
> >
> > Eric, will you do the honors? Since you did all the hard work before,
> > you derserve the fame as well. :)
>
> Since I am not sure either about xtensa I added chris to the cc list.
How about we just change all callers from arch/*/boot to use the _unsafe
version? Then..
> +/*
> + These two wrappers decide wheter strm->next_out gets checked for NULL.
> + The zlib_inflate_unsafe() version got added because the PPC zImage
> + gets extracted to memory address 0 and therefore
> + we avoid this check for zlib_inflate_unsafe()
These two wrappers decide wheter strm->next_out gets checked for NULL.
The zlib_inflate_unsafe() version is primarily used in the pre-Linux
'boot' directory code to allow for extraction to memory address 0 and
therefore we avoid this check.
--
Tom Rini
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-20 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 12:40 Bug with corrupted squashfs image Eric Sesterhenn
2009-01-16 17:45 ` [Patch] NULL pointer deref " Eric Sesterhenn
2009-01-16 19:07 ` Jörn Engel
2009-01-16 23:07 ` Tom Rini
2009-01-17 13:49 ` Jörn Engel
2009-01-17 19:38 ` Eric Sesterhenn
2009-01-20 16:47 ` Eric Sesterhenn
2009-01-20 17:57 ` Jörn Engel
2009-01-20 18:47 ` Tom Rini [this message]
2009-01-21 8:34 ` Eric Sesterhenn
2009-01-21 12:31 ` Phillip Lougher
2009-01-22 2:48 ` Phillip Lougher
2009-01-22 9:46 ` Jörn Engel
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=20090120184702.GB30203@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=chris@zankel.net \
--cc=jacmet@sunsite.dk \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=phillip@lougher.demon.co.uk \
--cc=rpurdie@rpsys.net \
--cc=snakebyte@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).