From: Ryusuke Konishi <ryusuke@osrg.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Subject: [GIT PULL] nilfs2 fixes for 2.6.30-rc6
Date: Wed, 13 May 2009 16:48:28 +0900 (JST) [thread overview]
Message-ID: <20090513.164828.56055985.ryusuke@osrg.net> (raw)
Hi Linus,
please pull nilfs2 bug-fixes from
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
The following changes since commit 091bf7624d1c90cec9e578a18529f615213ff847
Linus Torvalds (1):
Linux 2.6.30-rc5
Ryusuke Konishi (6):
nilfs2: fix possible recovery failure due to block creation without writer
nilfs2: fix circular locking dependency of writer mutex
nilfs2: ensure to clear dirty state when deleting metadata file block
nilfs2: fix possible circular locking for get information ioctls
nilfs2: fix lock order reversal in nilfs_clean_segments ioctl
nilfs2: check size of array structured data exchanged via ioctls
fs/nilfs2/ioctl.c | 281 ++++++++++++++++++++++++++------------------------
fs/nilfs2/mdt.c | 15 ++--
fs/nilfs2/nilfs.h | 3 +-
fs/nilfs2/page.c | 3 +-
fs/nilfs2/recovery.c | 6 +-
fs/nilfs2/segment.c | 5 +-
fs/nilfs2/segment.h | 3 +-
7 files changed, 167 insertions(+), 149 deletions(-)
-
The "nilfs2: check size of array structured data exchanged via ioctls"
adds missing sanity checks to ioctls. These checks are needed to
prevent memory access overrun in kernel code due to incorrect
argument data.
The "nilfs2: ensure to clear dirty state when deleting metadata file
block" fixes user-reported GC failures.
The "nilfs2: fix possible recovery failure due to block creation
without writer" fixes recovery failure on mount which can happen in a
boundary condition.
The "nilfs2: fix circular locking dependency of writer mutex",
"nilfs2: fix possible circular locking for get information ioctls", and
"nilfs2: fix lock order reversal in nilfs_clean_segments ioctl"
fix circular locking problems and lock order reversal the lockdep
check has detected.
Thanks,
Ryusuke Konishi
reply other threads:[~2009-05-13 7:49 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=20090513.164828.56055985.ryusuke@osrg.net \
--to=ryusuke@osrg.net \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--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®