From: "Jorge Boncompte [DTI2]" <jorge@dti2.net>
To: npiggin@suse.de
Cc: ext-adrian.hunter@nokia.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Error testing ext3 on brd ramdisk
Date: Fri, 13 Mar 2009 18:06:07 +0100 [thread overview]
Message-ID: <49BA927F.8020701@dti2.net> (raw)
In-Reply-To: <20090311021920.GA16561@wotan.suse.de>
Nick Piggin escribió:
> On Tue, Mar 10, 2009 at 05:49:13PM +0100, Jorge Boncompte [DTI2] wrote:
>> Nick Piggin escribió:
>>> Ah, of course, it would be due to directory-in-pagecache. You need
>>> the following patch if you expect this to work.
>>>
>>> And that confirms the ext3 problem is a different one because it
>>> doesn't use directory in pagecache I think. Well, I'll look at
>>> that one tomorrow.
>>>
>>> Thanks,
>>> Nick
>>>
>>> ---
>>> fs/super.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> Index: linux-2.6/fs/super.c
>>> ===================================================================
>>> --- linux-2.6.orig/fs/super.c
>>> +++ linux-2.6/fs/super.c
>>> @@ -644,6 +644,8 @@ int do_remount_sb(struct super_block *sb
>>> acct_auto_close(sb);
>>> shrink_dcache_sb(sb);
>>> fsync_super(sb);
>>> + if (flags & MS_RDONLY)
>>> + invalidate_bdev(sb->s_bdev);
>>>
>>> /* If we are remounting RDONLY and current sb is read/write,
>>> make sure there are no rw files opened */
>>>
>>>
>>>
>>>
>> With this applied it seems I cannot reproduce the corruption, I have
>
> Ah, that sounds promising.
>
>> to do more tests, but the box oopses on reboot after doing "umount -na -r".
>
> Oh, silly me, s_bdev will be NULL for non block device based filesystems.
> If you check for s_bdev != NULL there too, it should work.
Hi Nick, no problems noticed in the last days running with the below
patch...
--- linux-2.6.29-rc8/fs/super.c 2009-03-13 13:46:19 +0100
+++ kernel/fs/super.c 2009-03-13 13:47:50 +0100
@@ -647,6 +647,8 @@ int do_remount_sb(struct super_block *sb
acct_auto_close(sb);
shrink_dcache_sb(sb);
fsync_super(sb);
+ if (sb->s_bdev && (flags & MS_RDONLY))
+ invalidate_bdev(sb->s_bdev);
/* If we are remounting RDONLY and current sb is read/write,
make sure there are no rw files opened */
--
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5 14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be made.
==============================================================
next prev parent reply other threads:[~2009-03-13 17:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 13:25 Error testing ext3 on brd ramdisk Adrian Hunter
2009-02-27 18:08 ` Jorge Boncompte [DTI2]
2009-02-28 5:58 ` Nick Piggin
2009-03-02 17:42 ` Jorge Boncompte [DTI2]
2009-03-05 6:55 ` Nick Piggin
2009-03-05 9:19 ` Jorge Boncompte [DTI2]
2009-03-05 9:46 ` Nick Piggin
2009-03-05 10:56 ` Jorge Boncompte [DTI2]
2009-03-05 12:12 ` Jorge Boncompte [DTI2]
2009-03-10 16:12 ` Nick Piggin
2009-03-10 16:30 ` Nick Piggin
2009-03-10 16:49 ` Jorge Boncompte [DTI2]
2009-03-11 2:19 ` Nick Piggin
2009-03-13 17:06 ` Jorge Boncompte [DTI2] [this message]
2009-03-17 9:40 ` Denis Karpov
2009-03-18 12:11 ` Nick Piggin
2009-03-18 13:42 ` Jan Kara
2009-03-20 12:24 ` Denis Karpov
2009-03-20 12:49 ` Denis Karpov
2009-03-20 13:35 ` Denis Karpov
2009-03-05 10:45 ` Nick Piggin
2009-03-05 11:54 ` Jorge Boncompte [DTI2]
2009-03-06 7:47 ` Adrian Hunter
2009-03-10 11:03 ` Nick Piggin
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=49BA927F.8020701@dti2.net \
--to=jorge@dti2.net \
--cc=ext-adrian.hunter@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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