mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.31-rc3
Date: Sat, 11 Jul 2009 01:47:23 +0900 (JST)	[thread overview]
Message-ID: <20090711.014723.132733323.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

The following changes since commit 8e4a718ff38d8539938ec3421935904c27e00c39
 Linus Torvalds (1):
      Linux 2.6.31-rc2

Jiro SEKIBA (1):
      nilfs2: fix disorder in cp count on error during deleting checkpoints

Ryusuke Konishi (4):
      nilfs2: remove unlikely directive causing mis-conversion of error code
      nilfs2: fix hang problem of log writer which occurs after write failures
      nilfs2: fix incorrect KERN_CRIT messages in case of write failures
      nilfs2: fix lockdep warning between regular file and inode file

 fs/nilfs2/bmap.c    |    5 +++++
 fs/nilfs2/cpfile.c  |    5 ++---
 fs/nilfs2/dat.c     |    9 ---------
 fs/nilfs2/segment.c |   30 ++++++++----------------------
 4 files changed, 15 insertions(+), 34 deletions(-)
--

The "nilfs2: fix disorder in cp count on error during deleting
checkpoints" fixes a bug on error path which throws off checkpoint
count on disk.

The "nilfs2: fix hang problem of log writer which occurs after write
failures" fixes a reported hang problem.

The "nilfs2: remove unlikely directive causing mis-conversion of error code",
and "nilfs2: fix incorrect KERN_CRIT messages in case of write failures"
fix the related bugs.

The "nilfs2: fix lockdep warning between regular file and inode file"
fixes a false positive of lockdep check.

Thanks,
Ryusuke Konishi

                 reply	other threads:[~2009-07-10 16:48 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=20090711.014723.132733323.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 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®