From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
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.32-rc6
Date: Tue, 03 Nov 2009 16:49:07 +0900 (JST) [thread overview]
Message-ID: <20091103.164907.79138608.ryusuke@osrg.net> (raw)
Hi Linus,
please pull bug fixes of nilfs from:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
Containing a nontrivial fix to solve reported hang issue on ARM-based
targets. The other two fix an issue on checkpoint creation in small
footprint systems and missing buffer initialization, respectively.
--
The following changes since commit 1836d95928a0f41ada0cbb2a6c4e46b027db9491:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../ericvh/v9fs
Ryusuke Konishi (3):
nilfs2: fix dirty page accounting leak causing hang at write
nilfs2: fix irregular checkpoint creation due to data flush
nilfs2: add zero-fill for new btree node buffers
fs/nilfs2/btnode.c | 4 ++--
fs/nilfs2/segment.c | 19 ++++++++++++-------
2 files changed, 14 insertions(+), 9 deletions(-)
Thanks,
Ryusuke Konishi
reply other threads:[~2009-11-03 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=20091103.164907.79138608.ryusuke@osrg.net \
--to=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 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.