All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Squashfs fixes for 2.6.29?
Date: Thu, 05 Mar 2009 01:54:52 +0000	[thread overview]
Message-ID: <49AF30EC.8010205@lougher.demon.co.uk> (raw)

Hi Linus,

Please consider pulling the following Squashfs fixes.  They fix some 
potential oopses when dealing with corrupted filesystems (plus a trivial 
documentation typo fix).

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-linus.git

Phillip Lougher (2):
     Squashfs: Fix oops when reading fsfuzzer corrupted filesystems
     Squashfs: fix documentation typo, Cramfs filesystem limit is 256 MiB

Roel Kluin (1):
     Squashfs: frag_size should be signed, as it can hold an error result

  Documentation/filesystems/squashfs.txt |    2 +-
  fs/squashfs/block.c                    |   13 +++++++++++--
  fs/squashfs/cache.c                    |    4 ++--
  fs/squashfs/inode.c                    |    6 ++++--
  fs/squashfs/squashfs.h                 |    2 +-
  fs/squashfs/super.c                    |    2 +-
  6 files changed, 20 insertions(+), 9 deletions(-)

Thanks

Phillip

             reply	other threads:[~2009-03-05  1:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  1:54 Phillip Lougher [this message]
2009-03-09 21:39 ` [GIT PULL] Squashfs fixes for 2.6.29? Stefan Lippers-Hollmann
2009-03-10  2:13   ` Phillip Lougher
2009-03-10 11:02     ` Geert Uytterhoeven
2009-03-10 13:19       ` Woody Suwalski
2009-03-10 21:24       ` Stefan Lippers-Hollmann
2009-03-10 21:33       ` Phillip Lougher
2009-03-11  6:12         ` Phillip Lougher
2009-03-11 14:18           ` Geert Uytterhoeven
2009-03-11 20:46           ` Stefan Lippers-Hollmann
2009-03-10 20:02     ` Stefan Lippers-Hollmann

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=49AF30EC.8010205@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=torvalds@linux-foundation.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.