mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: torvalds@linux-foundation.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-karma-devel@lists.sourceforge.net
Subject: [GIT PULL] OMFS tree for 2.6.36
Date: Sun, 8 Aug 2010 15:22:13 -0400	[thread overview]
Message-ID: <20100808192213.GB11193@hash.localnet> (raw)

Hi Linus,

Please consider pulling these fixes for the OMFS file system.  This is my
first pull request for this tree, so do let me know if anything is amiss.

The patches include some I wrote quite a while ago when fuzz testing, along
with recent fixes for a memory leak and a compiler warning.  My small test
suite passes with all applied.

The following changes since commit 815c4163b6c8ebf8152f42b0a5fd015cfdcedc78:

  Linux 2.6.35-rc4 (2010-07-04 20:22:50 -0700)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/bcopeland/omfs.git for-linus

Bill Pemberton (1):
      omfs: fix uninitialized variable warning

Bob Copeland (3):
      omfs: check bounds on block numbers before passing to sb_bread
      omfs: refuse to mount if bitmap pointer is obviously wrong
      omfs: sanity check cluster size

Davidlohr Bueso (1):
      omfs: fix memory leak

 fs/omfs/dir.c     |   22 ++++++++--------------
 fs/omfs/file.c    |   10 +++++-----
 fs/omfs/inode.c   |   44 +++++++++++++++++++++++++++++++++-----------
 fs/omfs/omfs.h    |    1 +
 fs/omfs/omfs_fs.h |    1 +
 5 files changed, 48 insertions(+), 30 deletions(-)
-- 
Bob Copeland %% www.bobcopeland.com


                 reply	other threads:[~2010-08-08 19:31 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=20100808192213.GB11193@hash.localnet \
    --to=me@bobcopeland.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-karma-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 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®