mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: xb <xavier.bru@bull.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.12 quotaoff loop on a read-only ext3 filesystem
Date: Fri, 06 Jul 2007 11:41:30 +0200	[thread overview]
Message-ID: <468E0E4A.1010106@bull.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

Hi all,

Running on a 2.6.12.6 kernel, we found a problem with running quotaoff 
on an ext3 read-only filesystem:

quotaoff loops in dqput() because DQ_ACTIVE_B is set and 
ext3_release_dquot() returns because of ext3_journal_start() returning 
EROFS  without  calling dquot_release() that should have removed 
DQ_ACTIVE_B.
Then if we try to run the mount command to remount rw the file system, 
it deadlocks on the down_write(&s->s_umount) owned by quotaoff.
Has this problem been already identified and fixed in recent versions ?
Thanks in advance.

traces -------------------------------------------------------
/static int ext3_release_dquot(struct dquot *dquot)
{
...
    handle = ext3_journal_start(dquot_to_inode(dquot),
                    EXT3_QUOTA_INIT_BLOCKS);
    if (IS_ERR(handle))
        return PTR_ERR(handle); <------ returns here
    ret = dquot_release(dquot); <------- not executed
...
}/

/    <4>Backtrace of current task (pid 20974, quotaoff)
    <4>
    <4>Call Trace:
    <4> [<a00000010019ca10>] dqput+0x210/0x4e0
    <4>                                sp=e00000062a21fbe0 
bsp=e00000062a211198
    <4> [<a0000001001a15f0>] vfs_quota_off+0x590/0xca0
    <4>                                sp=e00000062a21fbe0 
bsp=e00000062a2110f8
    <4> [<a0000001001a5660>] sys_quotactl+0x1540/0x15e0
    <4> [<a00000010000b040>] ia64_ret_from_syscall+0x0/0x20
/
/    <4>mount         D a000000100547520     0 24222  
21243                     (NOTLB)
    <4>
    <4>Call Trace:
    <4> [<a000000100543ab0>] schedule+0xc10/0x23a0
    <4>                                sp=e00000055a5efaf0 
bsp=e00000055a5e1248
    <4> [<a000000100547520>] rwsem_down_write_failed+0x1c0/0x4e0
    <4>                                sp=e00000055a5efb30 
bsp=e00000055a5e1200
    <4> [<a000000100139930>] sget+0x6d0/0xb60
    <4>                                sp=e00000055a5efb50 
bsp=e00000055a5e1198
    <4> [<a00000010013b6d0>] get_sb_bdev+0xd0/0x400
    <4>                                sp=e00000055a5efb70 
bsp=e00000055a5e1148
    <4> [<a000000205508980>] ext3_get_sb+0x40/0x60 [ext3]
    <4>                                sp=e00000055a5efb90 
bsp=e00000055a5e1110
 <4> [<a00000010013bfe0>] do_kern_mount+0x140/0x480
   <4> [<a0000001001759f0>] do_mount+0x370/0x1060
    <4>                                sp=e00000055a5efb90 
bsp=e00000055a5e1060
   <4> [<a000000100177000>] sys_mount+0x100/0x1c0
  /


[-- Attachment #2: xavier.bru.vcf --]
[-- Type: text/x-vcard, Size: 293 bytes --]

begin:vcard
fn:Xavier Bru
n:Bru;Xavier
adr:;;1 rue de Provence, BP 208;38432 Echirolles Cedex;;;France
email;internet:Xavier.Bru@bull.net
title:BULL/HPC/linux/kernel
tel;work:+33 (0)4 76 29 77 45
tel;fax:+33 (0)4 76 29 77 70 
x-mozilla-html:TRUE
url:http://www.bull.com
version:2.1
end:vcard


                 reply	other threads:[~2007-07-06  9:41 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=468E0E4A.1010106@bull.net \
    --to=xavier.bru@bull.net \
    --cc=linux-kernel@vger.kernel.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®