From: Mingming Cao <cmm@us.ibm.com>
To: Christian Hesse <mail@eworm.de>
Cc: 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 07:58:23 -0700 [thread overview]
Message-ID: <1218725903.6749.3.camel@mingming-laptop> (raw)
In-Reply-To: <200808140859.03171.mail@eworm.de>
在 2008-08-14四的 08:59 +0200,Christian Hesse写道:
> On Thursday 14 August 2008, Theodore Tso wrote:
> > On Wed, Aug 13, 2008 at 05:10:53PM -0700, Mingming Cao wrote:
> > > I could reproduce it.
> > >
> > > This patch works for me on top of Ted's change. Christian, could you
> > > try it?
> >
> > Thanks, mingming! Looks good and I've added it to the patch queue.
>
> 08:58:16 eworm@io:~$ uptime
> 08:58:18 up 37 min, 2 users, load average: 3.57, 2.36, 1.12
>
> This is *a lot* longer than the system survived without the patches. I hope it
> is fixed now. Ted and Mingming, thanks a lot!
>
> A short side note... I get warnings when compiling the new code:
>
> fs/ext4/inode.c: In function 'ext4_da_release_space':
> fs/ext4/inode.c:1581: warning: format '%d' expects type 'int', but argument 2
> has type 'long unsigned int'
> fs/ext4/inode.c:1581: warning: format '%lu' expects type 'long unsigned int',
> but argument 3 has type 'int'
Thanks to all for quick verification of the fix.
Here is the fix for the compile warning . This compile warning fix has
be fold to the parent patch in ext4 patch queue :
fix-delalloc-release-block-reservation-for-truncate
http://repo.or.cz/w/ext4-patch-queue.git
Thanks,
Ming,ming
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;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-14 14:58 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 [this message]
2008-08-14 17:52 ` Aneesh Kumar K.V
[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=1218725903.6749.3.camel@mingming-laptop \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox