From: "Jörn Engel" <joern@logfs.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Eric Sesterhenn <snakebyte@gmx.de>,
phillip@lougher.demon.co.uk, linux-fsdevel@vger.kernel.org,
jacmet@sunsite.dk, rpurdie@rpsys.net
Subject: Re: [Patch] NULL pointer deref with corrupted squashfs image
Date: Sat, 17 Jan 2009 14:49:17 +0100 [thread overview]
Message-ID: <20090117134916.GA29641@logfs.org> (raw)
In-Reply-To: <20090116230700.GP6710@smtp.west.cox.net>
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. :)
Jörn
--
Joern's library part 11:
http://www.unicom.com/pw/reply-to-harmful.html
--
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-17 13:49 UTC|newest]
Thread overview: 18+ 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 [this message]
2009-01-17 19:38 ` Eric Sesterhenn
2009-01-20 16:47 ` Eric Sesterhenn
2009-01-20 16:47 ` Eric Sesterhenn
2009-01-20 17:57 ` Jörn Engel
2009-01-20 17:57 ` Jörn Engel
2009-01-20 18:47 ` Tom Rini
2009-01-20 18:47 ` Tom Rini
2009-01-21 8:34 ` Eric Sesterhenn
2009-01-21 8:34 ` Eric Sesterhenn
2009-01-21 12:31 ` Phillip Lougher
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=20090117134916.GA29641@logfs.org \
--to=joern@logfs.org \
--cc=jacmet@sunsite.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=rpurdie@rpsys.net \
--cc=snakebyte@gmx.de \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.