All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Christian Hesse <mail@eworm.de>, Theodore Tso <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: Re: Oops with ext4 from 2.6.27-rc3
Date: Thu, 14 Aug 2008 23:22:52 +0530	[thread overview]
Message-ID: <20080814175252.GA6397@skywalker> (raw)
In-Reply-To: <1218725903.6749.3.camel@mingming-laptop>

On Thu, Aug 14, 2008 at 07:58:23AM -0700, Mingming Cao wrote:
> 
> 
> Index: linux-2.6.27-rc3/fs/ext4/inode.c
> ===================================================================
> --- linux-2.6.27-rc3.orig/fs/ext4/inode.c	2008-08-14 07:49:14.000000000 -0700
> +++ linux-2.6.27-rc3/fs/ext4/inode.c	2008-08-14 07:49:45.000000000 -0700
> @@ -1576,7 +1576,7 @@ static void ext4_da_release_space(struct
>  		 */
>  		printk(KERN_INFO "ext4 delalloc try to release %d reserved"
>  			    "blocks for inode %lu, but there is no reserved"
> -			    "data blocks\n", inode->i_ino, to_free);
> +			    "data blocks\n", to_free, inode->i_ino);
>  		spin_unlock(&EXT4_I(inode)->i_block_reservation_lock);
>  		return;
>  	}


I guess you would need a space at the end of each lines.

		printk(KERN_INFO "ext4 delalloc try to release %d reserved "
			    "blocks for inode %lu, but there is no reserved "
			    "data blocks\n", to_free, inode->i_ino);
-aneesh

  reply	other threads:[~2008-08-14 17:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 18:28 Oops with ext4 from 2.6.27-rc3 eworm
2008-08-13 20:10 ` Theodore Tso
2008-08-13 20:55   ` Christian Hesse
2008-08-13 21:04     ` Theodore Tso
2008-08-13 21:07       ` Christian Hesse
2008-08-13 22:01         ` Theodore Tso
2008-08-13 22:19           ` Eric Sandeen
2008-08-13 22:45             ` Theodore Tso
2008-08-14  4:12               ` Rishikesh K Rajak
2008-08-14  0:10           ` Mingming Cao
2008-08-14  1:51             ` Theodore Tso
2008-08-14  6:59               ` Christian Hesse
2008-08-14 14:58                 ` Mingming Cao
2008-08-14 17:52                   ` Aneesh Kumar K.V [this message]
     [not found]             ` <216e58580808132159y53fc5403xb52839e1be2186a6@mail.gmail.com>
2008-08-14  5:39               ` Rishikesh K Rajak
2008-08-14  6:13               ` Christian Hesse
2008-08-14  6:16                 ` Rishikesh K Rajak
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13 21:03 Christian Hesse

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=20080814175252.GA6397@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mail@eworm.de \
    --cc=tytso@mit.edu \
    /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.