Re: [2.6.21] circular locking dependency found in QUOTA OFF
On Tue 15-05-07 19:52:03, Folkert van Heusden wrote:
> I'm afraid it doesn't compile:
>
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CHK include/linux/compile.h
> CC fs/dquot.o
> CC fs/quota.o
> fs/quota.c: In function `quota_sync_sb':
> fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this
> function)
> fs/quota.c:180: error: (Each undeclared identifier is reported only once
> fs/quota.c:180: error: for each function it appears in.)
> make[1]: *** [fs/quota.o] Error 1
> make: *** [fs] Error 2
Fixed patch follows (I messed up testing as I thought that lockdep is
under config option Debug mutexes but it is not...). I'm sorry for the
stupid mistake. Andrew, please discard my previous patch and use this new
one...
Honza
> On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
> > Hi,
> >
> > Thanks for report. It seems like a lockdep problem. i_mutex for quota
> > files is below dqonoff_sem. We were already fixing this for filesystem
> > specific quota IO functions but obviously we've missed a few cases. I
> > wonder why it showed up only now... Anyway, attached is a fix. Andrew,
> > would you add it? Thanks.
> >
> > Honza
> >
> > On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
> > > [adding Jan and fsdevel to CC]
> > >
> > > Hi Folkert,
> > >
> > > On 14/05/07, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> > > >Hi,
> > > >
> > > >When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
> > > >and system on an 1-filesystem IDE disk, I get the following circular
> > > >locking dependency error:
> > > >
> > > >[330961.226405] ===
> > > >[330961.226489] [ INFO: possible circular locking dependency detected ]
> > > >[330961.226531] 2.6.21 #5
> > > >[330961.226569] ---
> > > >[330961.226611] quotaoff/12249 is trying to acquire lock:
> > > >[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.226861]
> > > >[330961.226862] but task is already holding lock:
> > > >[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.227111]
> > > >[330961.227111] which lock already depends on the new lock.
> > > >[330961.227112]
> > > >[330961.227225]
> > > >[330961.227225] the existing dependency chain (in reverse order) is:
> > > >[330961.227303]
> > > >[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
> > > >[330961.227473][] check_prev_add+0x15b/0x281
> > > >[330961.227766][] check_prevs_add+0x8b/0xe8
> > > >[330961.228056][] __lock_acquire+0x692/0xb81
> > > >[330961.228353][] lock_acquire+0x62/0x81
> > > >[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
> > > >[330961.228934][] mutex_lock+0x8/0xa
> > > >[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
> > > >[330961.229513][] vfs_quota_on+0x75/0x79
> > > >[330961.229803][] ext3_quota_on+0x95/0xb0
> > > >[330961.230093][] do_quotactl+0xc9/0x2dd
> > > >[330961.230384][] sys_quotactl+0x84/0xd6
> > > >[330961.230673][] syscall_call+0x7/0xb
> > > >[330961.230963][] 0x
> > > >[330961.231268]
> > > >[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
> > > >[330961.231469][] check_prev_add+0x34/0x281
> > > >[330961.231759][] check_prevs_add+0x8b/0xe8
> > > >[330961.232049][] __lock_acquire+0x692/0xb81
> > > >[330961.232344][] lock_acquire+0x62/0x81
> > > >[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
> > > >[330961.232923][] mutex_lock+0x8/0xa
> > > >[330961.233211][] vfs_quota_off+0x1cf/0x260
> > > >[330961.233500][] do_quotactl+0x29f/0x2dd
> > > >[330961.233792][] sys_quotactl+0x84/0xd6
> > > >[330961.234081][] syscall_call+0x7/0xb
> > > >[330961.234503][] 0x
> > > >[330961.234795]
> > > >[330961.234795] other info that might help us debug this:
> > > >[330961.234796]
> > > >[330961.234908] 2 locks held by quotaoff/12249:
> > > >[330961.234947] #0: (>s_umount_key#15){}, at: []
> > > >get_super+0x53/0x94
> > > >[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.235386]
> > > >[330961.235387] stack backtrace:
> > > >[330961.235462] [] show_trace_log_lvl+0x1a/0x30
> > > >[330961.235535] [] show_trace+0x12/0x14
> > > >[330961.235606] [] dump_stack+0x16/0x18
> > > >[330961.235679] [] print_circular_bug_tail+0x6f/0x71
> > > >[330961.235753] [] check_prev_add+0x34/0x281
> > > >[330961.235825] [] check_prevs_add+0x8b/0xe8
> > > >[330961.235897] [] __lock_acquire+0x692/0xb81
> > > >[330961.235969] [] lock_acquire+0x62/0x81
> > > >[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
> > >
Re: [2.6.21] circular locking dependency found in QUOTA OFF
On Tue 15-05-07 19:52:03, Folkert van Heusden wrote:
> I'm afraid it doesn't compile:
>
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CHK include/linux/compile.h
> CC fs/dquot.o
> CC fs/quota.o
> fs/quota.c: In function `quota_sync_sb':
> fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this
> function)
> fs/quota.c:180: error: (Each undeclared identifier is reported only once
> fs/quota.c:180: error: for each function it appears in.)
> make[1]: *** [fs/quota.o] Error 1
> make: *** [fs] Error 2
Huh, I has compiled just fine for me... Can you send me your .config?
Thanks.
Honza
> On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
> > Hi,
> >
> > Thanks for report. It seems like a lockdep problem. i_mutex for quota
> > files is below dqonoff_sem. We were already fixing this for filesystem
> > specific quota IO functions but obviously we've missed a few cases. I
> > wonder why it showed up only now... Anyway, attached is a fix. Andrew,
> > would you add it? Thanks.
> >
> > Honza
> >
> > On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
> > > [adding Jan and fsdevel to CC]
> > >
> > > Hi Folkert,
> > >
> > > On 14/05/07, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> > > >Hi,
> > > >
> > > >When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
> > > >and system on an 1-filesystem IDE disk, I get the following circular
> > > >locking dependency error:
> > > >
> > > >[330961.226405] ===
> > > >[330961.226489] [ INFO: possible circular locking dependency detected ]
> > > >[330961.226531] 2.6.21 #5
> > > >[330961.226569] ---
> > > >[330961.226611] quotaoff/12249 is trying to acquire lock:
> > > >[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.226861]
> > > >[330961.226862] but task is already holding lock:
> > > >[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.227111]
> > > >[330961.227111] which lock already depends on the new lock.
> > > >[330961.227112]
> > > >[330961.227225]
> > > >[330961.227225] the existing dependency chain (in reverse order) is:
> > > >[330961.227303]
> > > >[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
> > > >[330961.227473][] check_prev_add+0x15b/0x281
> > > >[330961.227766][] check_prevs_add+0x8b/0xe8
> > > >[330961.228056][] __lock_acquire+0x692/0xb81
> > > >[330961.228353][] lock_acquire+0x62/0x81
> > > >[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
> > > >[330961.228934][] mutex_lock+0x8/0xa
> > > >[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
> > > >[330961.229513][] vfs_quota_on+0x75/0x79
> > > >[330961.229803][] ext3_quota_on+0x95/0xb0
> > > >[330961.230093][] do_quotactl+0xc9/0x2dd
> > > >[330961.230384][] sys_quotactl+0x84/0xd6
> > > >[330961.230673][] syscall_call+0x7/0xb
> > > >[330961.230963][] 0x
> > > >[330961.231268]
> > > >[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
> > > >[330961.231469][] check_prev_add+0x34/0x281
> > > >[330961.231759][] check_prevs_add+0x8b/0xe8
> > > >[330961.232049][] __lock_acquire+0x692/0xb81
> > > >[330961.232344][] lock_acquire+0x62/0x81
> > > >[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
> > > >[330961.232923][] mutex_lock+0x8/0xa
> > > >[330961.233211][] vfs_quota_off+0x1cf/0x260
> > > >[330961.233500][] do_quotactl+0x29f/0x2dd
> > > >[330961.233792][] sys_quotactl+0x84/0xd6
> > > >[330961.234081][] syscall_call+0x7/0xb
> > > >[330961.234503][] 0x
> > > >[330961.234795]
> > > >[330961.234795] other info that might help us debug this:
> > > >[330961.234796]
> > > >[330961.234908] 2 locks held by quotaoff/12249:
> > > >[330961.234947] #0: (>s_umount_key#15){}, at: []
> > > >get_super+0x53/0x94
> > > >[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
> > > >mutex_lock+0x8/0xa
> > > >[330961.235386]
> > > >[330961.235387] stack backtrace:
> > > >[330961.235462] [] show_trace_log_lvl+0x1a/0x30
> > > >[330961.235535] [] show_trace+0x12/0x14
> > > >[330961.235606] [] dump_stack+0x16/0x18
> > > >[330961.235679] [] print_circular_bug_tail+0x6f/0x71
> > > >[330961.235753] [] check_prev_add+0x34/0x281
> > > >[330961.235825] [] check_prevs_add+0x8b/0xe8
> > > >[330961.235897] [] __lock_acquire+0x692/0xb81
> > > >[330961.235969] [] lock_acquire+0x62/0x81
> > > >[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
> > > >[330961.236113] [] mutex_lock+0x8/0xa
> > > >[330961.236185] [] vfs_quota_off+0x1cf/0x260
> > > >[330961.236257] []
Re: [2.6.21] circular locking dependency found in QUOTA OFF
I'm afraid it doesn't compile:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC fs/dquot.o
CC fs/quota.o
fs/quota.c: In function `quota_sync_sb':
fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this function)
fs/quota.c:180: error: (Each undeclared identifier is reported only once
fs/quota.c:180: error: for each function it appears in.)
make[1]: *** [fs/quota.o] Error 1
make: *** [fs] Error 2
On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
> Hi,
>
> Thanks for report. It seems like a lockdep problem. i_mutex for quota
> files is below dqonoff_sem. We were already fixing this for filesystem
> specific quota IO functions but obviously we've missed a few cases. I
> wonder why it showed up only now... Anyway, attached is a fix. Andrew,
> would you add it? Thanks.
>
> Honza
>
> On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
> > [adding Jan and fsdevel to CC]
> >
> > Hi Folkert,
> >
> > On 14/05/07, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> > >Hi,
> > >
> > >When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
> > >and system on an 1-filesystem IDE disk, I get the following circular
> > >locking dependency error:
> > >
> > >[330961.226405] ===
> > >[330961.226489] [ INFO: possible circular locking dependency detected ]
> > >[330961.226531] 2.6.21 #5
> > >[330961.226569] ---
> > >[330961.226611] quotaoff/12249 is trying to acquire lock:
> > >[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
> > >mutex_lock+0x8/0xa
> > >[330961.226861]
> > >[330961.226862] but task is already holding lock:
> > >[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
> > >mutex_lock+0x8/0xa
> > >[330961.227111]
> > >[330961.227111] which lock already depends on the new lock.
> > >[330961.227112]
> > >[330961.227225]
> > >[330961.227225] the existing dependency chain (in reverse order) is:
> > >[330961.227303]
> > >[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
> > >[330961.227473][] check_prev_add+0x15b/0x281
> > >[330961.227766][] check_prevs_add+0x8b/0xe8
> > >[330961.228056][] __lock_acquire+0x692/0xb81
> > >[330961.228353][] lock_acquire+0x62/0x81
> > >[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
> > >[330961.228934][] mutex_lock+0x8/0xa
> > >[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
> > >[330961.229513][] vfs_quota_on+0x75/0x79
> > >[330961.229803][] ext3_quota_on+0x95/0xb0
> > >[330961.230093][] do_quotactl+0xc9/0x2dd
> > >[330961.230384][] sys_quotactl+0x84/0xd6
> > >[330961.230673][] syscall_call+0x7/0xb
> > >[330961.230963][] 0x
> > >[330961.231268]
> > >[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
> > >[330961.231469][] check_prev_add+0x34/0x281
> > >[330961.231759][] check_prevs_add+0x8b/0xe8
> > >[330961.232049][] __lock_acquire+0x692/0xb81
> > >[330961.232344][] lock_acquire+0x62/0x81
> > >[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
> > >[330961.232923][] mutex_lock+0x8/0xa
> > >[330961.233211][] vfs_quota_off+0x1cf/0x260
> > >[330961.233500][] do_quotactl+0x29f/0x2dd
> > >[330961.233792][] sys_quotactl+0x84/0xd6
> > >[330961.234081][] syscall_call+0x7/0xb
> > >[330961.234503][] 0x
> > >[330961.234795]
> > >[330961.234795] other info that might help us debug this:
> > >[330961.234796]
> > >[330961.234908] 2 locks held by quotaoff/12249:
> > >[330961.234947] #0: (>s_umount_key#15){}, at: []
> > >get_super+0x53/0x94
> > >[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
> > >mutex_lock+0x8/0xa
> > >[330961.235386]
> > >[330961.235387] stack backtrace:
> > >[330961.235462] [] show_trace_log_lvl+0x1a/0x30
> > >[330961.235535] [] show_trace+0x12/0x14
> > >[330961.235606] [] dump_stack+0x16/0x18
> > >[330961.235679] [] print_circular_bug_tail+0x6f/0x71
> > >[330961.235753] [] check_prev_add+0x34/0x281
> > >[330961.235825] [] check_prevs_add+0x8b/0xe8
> > >[330961.235897] [] __lock_acquire+0x692/0xb81
> > >[330961.235969] [] lock_acquire+0x62/0x81
> > >[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
> > >[330961.236113] [] mutex_lock+0x8/0xa
> > >[330961.236185] [] vfs_quota_off+0x1cf/0x260
> > >[330961.236257] [] do_quotactl+0x29f/0x2dd
> > >[330961.236330] [] sys_quotactl+0x84/0xd6
> > >[330961.236402] [] syscall_call+0x7/0xb
> > >[330961.236473] ===
> > >
> >
> > Is this a 2.6.21 regression?
> >
> > Regards,
> > Michal
> >
> > --
> > Michal K. K. Piotrowski
> > Kernel Monkeys
> > (http://kernel.wikidot.com/start)
> --
> Jan Kara <[EMAIL PROTECTED]>
> SuSE CR Labs
> i_mutex on quota files is special. Unlike
Re: [2.6.21] circular locking dependency found in QUOTA OFF
Hi,
Thanks for report. It seems like a lockdep problem. i_mutex for quota
files is below dqonoff_sem. We were already fixing this for filesystem
specific quota IO functions but obviously we've missed a few cases. I
wonder why it showed up only now... Anyway, attached is a fix. Andrew,
would you add it? Thanks.
Honza
On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
> [adding Jan and fsdevel to CC]
>
> Hi Folkert,
>
> On 14/05/07, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
> >and system on an 1-filesystem IDE disk, I get the following circular
> >locking dependency error:
> >
> >[330961.226405] ===
> >[330961.226489] [ INFO: possible circular locking dependency detected ]
> >[330961.226531] 2.6.21 #5
> >[330961.226569] ---
> >[330961.226611] quotaoff/12249 is trying to acquire lock:
> >[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
> >mutex_lock+0x8/0xa
> >[330961.226861]
> >[330961.226862] but task is already holding lock:
> >[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
> >mutex_lock+0x8/0xa
> >[330961.227111]
> >[330961.227111] which lock already depends on the new lock.
> >[330961.227112]
> >[330961.227225]
> >[330961.227225] the existing dependency chain (in reverse order) is:
> >[330961.227303]
> >[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
> >[330961.227473][] check_prev_add+0x15b/0x281
> >[330961.227766][] check_prevs_add+0x8b/0xe8
> >[330961.228056][] __lock_acquire+0x692/0xb81
> >[330961.228353][] lock_acquire+0x62/0x81
> >[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
> >[330961.228934][] mutex_lock+0x8/0xa
> >[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
> >[330961.229513][] vfs_quota_on+0x75/0x79
> >[330961.229803][] ext3_quota_on+0x95/0xb0
> >[330961.230093][] do_quotactl+0xc9/0x2dd
> >[330961.230384][] sys_quotactl+0x84/0xd6
> >[330961.230673][] syscall_call+0x7/0xb
> >[330961.230963][] 0x
> >[330961.231268]
> >[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
> >[330961.231469][] check_prev_add+0x34/0x281
> >[330961.231759][] check_prevs_add+0x8b/0xe8
> >[330961.232049][] __lock_acquire+0x692/0xb81
> >[330961.232344][] lock_acquire+0x62/0x81
> >[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
> >[330961.232923][] mutex_lock+0x8/0xa
> >[330961.233211][] vfs_quota_off+0x1cf/0x260
> >[330961.233500][] do_quotactl+0x29f/0x2dd
> >[330961.233792][] sys_quotactl+0x84/0xd6
> >[330961.234081][] syscall_call+0x7/0xb
> >[330961.234503][] 0x
> >[330961.234795]
> >[330961.234795] other info that might help us debug this:
> >[330961.234796]
> >[330961.234908] 2 locks held by quotaoff/12249:
> >[330961.234947] #0: (>s_umount_key#15){}, at: []
> >get_super+0x53/0x94
> >[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
> >mutex_lock+0x8/0xa
> >[330961.235386]
> >[330961.235387] stack backtrace:
> >[330961.235462] [] show_trace_log_lvl+0x1a/0x30
> >[330961.235535] [] show_trace+0x12/0x14
> >[330961.235606] [] dump_stack+0x16/0x18
> >[330961.235679] [] print_circular_bug_tail+0x6f/0x71
> >[330961.235753] [] check_prev_add+0x34/0x281
> >[330961.235825] [] check_prevs_add+0x8b/0xe8
> >[330961.235897] [] __lock_acquire+0x692/0xb81
> >[330961.235969] [] lock_acquire+0x62/0x81
> >[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
> >[330961.236113] [] mutex_lock+0x8/0xa
> >[330961.236185] [] vfs_quota_off+0x1cf/0x260
> >[330961.236257] [] do_quotactl+0x29f/0x2dd
> >[330961.236330] [] sys_quotactl+0x84/0xd6
> >[330961.236402] [] syscall_call+0x7/0xb
> >[330961.236473] ===
> >
>
> Is this a 2.6.21 regression?
>
> Regards,
> Michal
>
> --
> Michal K. K. Piotrowski
> Kernel Monkeys
> (http://kernel.wikidot.com/start)
--
Jan Kara <[EMAIL PROTECTED]>
SuSE CR Labs
i_mutex on quota files is special. Unlike i_mutexes for other inodes it is
acquired under dqonoff_mutex. Tell lockdep about this lock ranking. Also
comment and code in quota_sync_sb() seem to be bogus (as i_mutex for quota
file can be acquired under dqonoff_mutex). Move truncate_inode_pages()
call under dqonoff_mutex and save some problems with races...
Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
diff -rupX /home/jack/.kerndiffexclude linux-2.6.21/fs/dquot.c linux-2.6.21-1-quota_lockdep/fs/dquot.c
--- linux-2.6.21/fs/dquot.c 2007-05-15 14:18:47.0 +0200
+++ linux-2.6.21-1-quota_lockdep/fs/dquot.c 2007-05-15 14:22:47.0 +0200
@@ -1421,7 +1421,7 @@ int vfs_quota_off(struct super_block *sb
/* If quota was reenabled in the meantime, we have
* nothing to do */
if
Re: [2.6.21] circular locking dependency found in QUOTA OFF
Hi,
Thanks for report. It seems like a lockdep problem. i_mutex for quota
files is below dqonoff_sem. We were already fixing this for filesystem
specific quota IO functions but obviously we've missed a few cases. I
wonder why it showed up only now... Anyway, attached is a fix. Andrew,
would you add it? Thanks.
Honza
On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden [EMAIL PROTECTED] wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
[330961.236330] [c10a214a] sys_quotactl+0x84/0xd6
[330961.236402] [c1003f74] syscall_call+0x7/0xb
[330961.236473] ===
Is this a 2.6.21 regression?
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
--
Jan Kara [EMAIL PROTECTED]
SuSE CR Labs
i_mutex on quota files is special. Unlike i_mutexes for other inodes it is
acquired under dqonoff_mutex. Tell lockdep about this lock ranking. Also
comment and code in quota_sync_sb() seem to be bogus (as i_mutex for quota
file can be acquired under dqonoff_mutex). Move truncate_inode_pages()
call under dqonoff_mutex and save some problems with races...
Signed-off-by: Jan Kara [EMAIL PROTECTED]
diff -rupX /home/jack/.kerndiffexclude linux-2.6.21/fs/dquot.c linux-2.6.21-1-quota_lockdep/fs/dquot.c
--- linux-2.6.21/fs/dquot.c 2007-05-15 14:18:47.0 +0200
+++ linux-2.6.21-1-quota_lockdep/fs/dquot.c 2007-05-15
Re: [2.6.21] circular locking dependency found in QUOTA OFF
I'm afraid it doesn't compile:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC fs/dquot.o
CC fs/quota.o
fs/quota.c: In function `quota_sync_sb':
fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this function)
fs/quota.c:180: error: (Each undeclared identifier is reported only once
fs/quota.c:180: error: for each function it appears in.)
make[1]: *** [fs/quota.o] Error 1
make: *** [fs] Error 2
On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
Hi,
Thanks for report. It seems like a lockdep problem. i_mutex for quota
files is below dqonoff_sem. We were already fixing this for filesystem
specific quota IO functions but obviously we've missed a few cases. I
wonder why it showed up only now... Anyway, attached is a fix. Andrew,
would you add it? Thanks.
Honza
On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden [EMAIL PROTECTED] wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
[330961.236330] [c10a214a] sys_quotactl+0x84/0xd6
[330961.236402] [c1003f74] syscall_call+0x7/0xb
[330961.236473] ===
Is this a 2.6.21 regression?
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
--
Jan Kara [EMAIL
Re: [2.6.21] circular locking dependency found in QUOTA OFF
On Tue 15-05-07 19:52:03, Folkert van Heusden wrote:
I'm afraid it doesn't compile:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC fs/dquot.o
CC fs/quota.o
fs/quota.c: In function `quota_sync_sb':
fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this
function)
fs/quota.c:180: error: (Each undeclared identifier is reported only once
fs/quota.c:180: error: for each function it appears in.)
make[1]: *** [fs/quota.o] Error 1
make: *** [fs] Error 2
Huh, I has compiled just fine for me... Can you send me your .config?
Thanks.
Honza
On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
Hi,
Thanks for report. It seems like a lockdep problem. i_mutex for quota
files is below dqonoff_sem. We were already fixing this for filesystem
specific quota IO functions but obviously we've missed a few cases. I
wonder why it showed up only now... Anyway, attached is a fix. Andrew,
would you add it? Thanks.
Honza
On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden [EMAIL PROTECTED] wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
Re: [2.6.21] circular locking dependency found in QUOTA OFF
On Tue 15-05-07 19:52:03, Folkert van Heusden wrote:
I'm afraid it doesn't compile:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC fs/dquot.o
CC fs/quota.o
fs/quota.c: In function `quota_sync_sb':
fs/quota.c:180: error: `I_MUTEX_NESTED' undeclared (first use in this
function)
fs/quota.c:180: error: (Each undeclared identifier is reported only once
fs/quota.c:180: error: for each function it appears in.)
make[1]: *** [fs/quota.o] Error 1
make: *** [fs] Error 2
Fixed patch follows (I messed up testing as I thought that lockdep is
under config option Debug mutexes but it is not...). I'm sorry for the
stupid mistake. Andrew, please discard my previous patch and use this new
one...
Honza
On Tue, May 15, 2007 at 04:09:39PM +0200, Jan Kara wrote:
Hi,
Thanks for report. It seems like a lockdep problem. i_mutex for quota
files is below dqonoff_sem. We were already fixing this for filesystem
specific quota IO functions but obviously we've missed a few cases. I
wonder why it showed up only now... Anyway, attached is a fix. Andrew,
would you add it? Thanks.
Honza
On Mon 14-05-07 19:43:18, Michal Piotrowski wrote:
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden [EMAIL PROTECTED] wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1]
Re: [2.6.21] circular locking dependency found in QUOTA OFF
> [adding Jan and fsdevel to CC] > Hi Folkert, > >When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram > >and system on an 1-filesystem IDE disk, I get the following circular > >locking dependency error: > > > >[330961.226405] === > >[330961.226489] [ INFO: possible circular locking dependency detected ] > >[330961.226531] 2.6.21 #5 ... > >[330961.236402] [] syscall_call+0x7/0xb > >[330961.236473] === > > Is this a 2.6.21 regression? This is new for 2.6.21, yes. Folkert van Heusden -- MultiTail est un flexible tool pour suivre de logfiles et execution de commandements. Filtrer, pourvoir de couleur, merge, 'diff-view', etc. http://www.vanheusden.com/multitail/ -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.21] circular locking dependency found in QUOTA OFF
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
[330961.227473][] check_prev_add+0x15b/0x281
[330961.227766][] check_prevs_add+0x8b/0xe8
[330961.228056][] __lock_acquire+0x692/0xb81
[330961.228353][] lock_acquire+0x62/0x81
[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][] mutex_lock+0x8/0xa
[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][] vfs_quota_on+0x75/0x79
[330961.229803][] ext3_quota_on+0x95/0xb0
[330961.230093][] do_quotactl+0xc9/0x2dd
[330961.230384][] sys_quotactl+0x84/0xd6
[330961.230673][] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
[330961.231469][] check_prev_add+0x34/0x281
[330961.231759][] check_prevs_add+0x8b/0xe8
[330961.232049][] __lock_acquire+0x692/0xb81
[330961.232344][] lock_acquire+0x62/0x81
[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][] mutex_lock+0x8/0xa
[330961.233211][] vfs_quota_off+0x1cf/0x260
[330961.233500][] do_quotactl+0x29f/0x2dd
[330961.233792][] sys_quotactl+0x84/0xd6
[330961.234081][] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (>s_umount_key#15){}, at: []
get_super+0x53/0x94
[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [] show_trace_log_lvl+0x1a/0x30
[330961.235535] [] show_trace+0x12/0x14
[330961.235606] [] dump_stack+0x16/0x18
[330961.235679] [] print_circular_bug_tail+0x6f/0x71
[330961.235753] [] check_prev_add+0x34/0x281
[330961.235825] [] check_prevs_add+0x8b/0xe8
[330961.235897] [] __lock_acquire+0x692/0xb81
[330961.235969] [] lock_acquire+0x62/0x81
[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [] mutex_lock+0x8/0xa
[330961.236185] [] vfs_quota_off+0x1cf/0x260
[330961.236257] [] do_quotactl+0x29f/0x2dd
[330961.236330] [] sys_quotactl+0x84/0xd6
[330961.236402] [] syscall_call+0x7/0xb
[330961.236473] ===
Is this a 2.6.21 regression?
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[2.6.21] circular locking dependency found in QUOTA OFF
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
[330961.227473][] check_prev_add+0x15b/0x281
[330961.227766][] check_prevs_add+0x8b/0xe8
[330961.228056][] __lock_acquire+0x692/0xb81
[330961.228353][] lock_acquire+0x62/0x81
[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][] mutex_lock+0x8/0xa
[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][] vfs_quota_on+0x75/0x79
[330961.229803][] ext3_quota_on+0x95/0xb0
[330961.230093][] do_quotactl+0xc9/0x2dd
[330961.230384][] sys_quotactl+0x84/0xd6
[330961.230673][] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
[330961.231469][] check_prev_add+0x34/0x281
[330961.231759][] check_prevs_add+0x8b/0xe8
[330961.232049][] __lock_acquire+0x692/0xb81
[330961.232344][] lock_acquire+0x62/0x81
[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][] mutex_lock+0x8/0xa
[330961.233211][] vfs_quota_off+0x1cf/0x260
[330961.233500][] do_quotactl+0x29f/0x2dd
[330961.233792][] sys_quotactl+0x84/0xd6
[330961.234081][] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (>s_umount_key#15){}, at: []
get_super+0x53/0x94
[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [] show_trace_log_lvl+0x1a/0x30
[330961.235535] [] show_trace+0x12/0x14
[330961.235606] [] dump_stack+0x16/0x18
[330961.235679] [] print_circular_bug_tail+0x6f/0x71
[330961.235753] [] check_prev_add+0x34/0x281
[330961.235825] [] check_prevs_add+0x8b/0xe8
[330961.235897] [] __lock_acquire+0x692/0xb81
[330961.235969] [] lock_acquire+0x62/0x81
[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [] mutex_lock+0x8/0xa
[330961.236185] [] vfs_quota_off+0x1cf/0x260
[330961.236257] [] do_quotactl+0x29f/0x2dd
[330961.236330] [] sys_quotactl+0x84/0xd6
[330961.236402] [] syscall_call+0x7/0xb
[330961.236473] ===
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[2.6.21] circular locking dependency found in QUOTA OFF
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (>s_type->i_mutex_key#4){--..}, at: []
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] -> #1 (>s_dquot.dqonoff_mutex){--..}:
[330961.227473][] check_prev_add+0x15b/0x281
[330961.227766][] check_prevs_add+0x8b/0xe8
[330961.228056][] __lock_acquire+0x692/0xb81
[330961.228353][] lock_acquire+0x62/0x81
[330961.228643][] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][] mutex_lock+0x8/0xa
[330961.229221][] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][] vfs_quota_on+0x75/0x79
[330961.229803][] ext3_quota_on+0x95/0xb0
[330961.230093][] do_quotactl+0xc9/0x2dd
[330961.230384][] sys_quotactl+0x84/0xd6
[330961.230673][] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] -> #0 (>s_type->i_mutex_key#4){--..}:
[330961.231469][] check_prev_add+0x34/0x281
[330961.231759][] check_prevs_add+0x8b/0xe8
[330961.232049][] __lock_acquire+0x692/0xb81
[330961.232344][] lock_acquire+0x62/0x81
[330961.232632][] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][] mutex_lock+0x8/0xa
[330961.233211][] vfs_quota_off+0x1cf/0x260
[330961.233500][] do_quotactl+0x29f/0x2dd
[330961.233792][] sys_quotactl+0x84/0xd6
[330961.234081][] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (>s_umount_key#15){}, at: []
get_super+0x53/0x94
[330961.235183] #1: (>s_dquot.dqonoff_mutex){--..}, at: []
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [] show_trace_log_lvl+0x1a/0x30
[330961.235535] [] show_trace+0x12/0x14
[330961.235606] [] dump_stack+0x16/0x18
[330961.235679] [] print_circular_bug_tail+0x6f/0x71
[330961.235753] [] check_prev_add+0x34/0x281
[330961.235825] [] check_prevs_add+0x8b/0xe8
[330961.235897] [] __lock_acquire+0x692/0xb81
[330961.235969] [] lock_acquire+0x62/0x81
[330961.236041] [] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [] mutex_lock+0x8/0xa
[330961.236185] [] vfs_quota_off+0x1cf/0x260
[330961.236257] [] do_quotactl+0x29f/0x2dd
[330961.236330] [] sys_quotactl+0x84/0xd6
[330961.236402] [] syscall_call+0x7/0xb
[330961.236473] ===
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[2.6.21] circular locking dependency found in QUOTA OFF
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
[330961.236330] [c10a214a] sys_quotactl+0x84/0xd6
[330961.236402] [c1003f74] syscall_call+0x7/0xb
[330961.236473] ===
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[2.6.21] circular locking dependency found in QUOTA OFF
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
[330961.236330] [c10a214a] sys_quotactl+0x84/0xd6
[330961.236402] [c1003f74] syscall_call+0x7/0xb
[330961.236473] ===
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.21] circular locking dependency found in QUOTA OFF
[adding Jan and fsdevel to CC]
Hi Folkert,
On 14/05/07, Folkert van Heusden [EMAIL PROTECTED] wrote:
Hi,
When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram
and system on an 1-filesystem IDE disk, I get the following circular
locking dependency error:
[330961.226405] ===
[330961.226489] [ INFO: possible circular locking dependency detected ]
[330961.226531] 2.6.21 #5
[330961.226569] ---
[330961.226611] quotaoff/12249 is trying to acquire lock:
[330961.226652] (sb-s_type-i_mutex_key#4){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.226861]
[330961.226862] but task is already holding lock:
[330961.226938] (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.227111]
[330961.227111] which lock already depends on the new lock.
[330961.227112]
[330961.227225]
[330961.227225] the existing dependency chain (in reverse order) is:
[330961.227303]
[330961.227303] - #1 (s-s_dquot.dqonoff_mutex){--..}:
[330961.227473][c1039b02] check_prev_add+0x15b/0x281
[330961.227766][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.228056][c103b683] __lock_acquire+0x692/0xb81
[330961.228353][c103bfda] lock_acquire+0x62/0x81
[330961.228643][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.228934][c120e2a1] mutex_lock+0x8/0xa
[330961.229221][c109fbbe] vfs_quota_on_inode+0xc1/0x25f
[330961.229513][c109fdd1] vfs_quota_on+0x75/0x79
[330961.229803][c10bc92d] ext3_quota_on+0x95/0xb0
[330961.230093][c10a1eb2] do_quotactl+0xc9/0x2dd
[330961.230384][c10a214a] sys_quotactl+0x84/0xd6
[330961.230673][c1003f74] syscall_call+0x7/0xb
[330961.230963][] 0x
[330961.231268]
[330961.231268] - #0 (sb-s_type-i_mutex_key#4){--..}:
[330961.231469][c10399db] check_prev_add+0x34/0x281
[330961.231759][c1039cb3] check_prevs_add+0x8b/0xe8
[330961.232049][c103b683] __lock_acquire+0x692/0xb81
[330961.232344][c103bfda] lock_acquire+0x62/0x81
[330961.232632][c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.232923][c120e2a1] mutex_lock+0x8/0xa
[330961.233211][c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.233500][c10a2088] do_quotactl+0x29f/0x2dd
[330961.233792][c10a214a] sys_quotactl+0x84/0xd6
[330961.234081][c1003f74] syscall_call+0x7/0xb
[330961.234503][] 0x
[330961.234795]
[330961.234795] other info that might help us debug this:
[330961.234796]
[330961.234908] 2 locks held by quotaoff/12249:
[330961.234947] #0: (type-s_umount_key#15){}, at: [c1070b5d]
get_super+0x53/0x94
[330961.235183] #1: (s-s_dquot.dqonoff_mutex){--..}, at: [c120e2a1]
mutex_lock+0x8/0xa
[330961.235386]
[330961.235387] stack backtrace:
[330961.235462] [c1004d53] show_trace_log_lvl+0x1a/0x30
[330961.235535] [c1004d7b] show_trace+0x12/0x14
[330961.235606] [c1004e75] dump_stack+0x16/0x18
[330961.235679] [c1039352] print_circular_bug_tail+0x6f/0x71
[330961.235753] [c10399db] check_prev_add+0x34/0x281
[330961.235825] [c1039cb3] check_prevs_add+0x8b/0xe8
[330961.235897] [c103b683] __lock_acquire+0x692/0xb81
[330961.235969] [c103bfda] lock_acquire+0x62/0x81
[330961.236041] [c120e322] __mutex_lock_slowpath+0x75/0x28c
[330961.236113] [c120e2a1] mutex_lock+0x8/0xa
[330961.236185] [c109fa6c] vfs_quota_off+0x1cf/0x260
[330961.236257] [c10a2088] do_quotactl+0x29f/0x2dd
[330961.236330] [c10a214a] sys_quotactl+0x84/0xd6
[330961.236402] [c1003f74] syscall_call+0x7/0xb
[330961.236473] ===
Is this a 2.6.21 regression?
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.21] circular locking dependency found in QUOTA OFF
[adding Jan and fsdevel to CC] Hi Folkert, When I cleanly reboot my pc running 2.6.21 on a P4 with HT and 2GB of ram and system on an 1-filesystem IDE disk, I get the following circular locking dependency error: [330961.226405] === [330961.226489] [ INFO: possible circular locking dependency detected ] [330961.226531] 2.6.21 #5 ... [330961.236402] [c1003f74] syscall_call+0x7/0xb [330961.236473] === Is this a 2.6.21 regression? This is new for 2.6.21, yes. Folkert van Heusden -- MultiTail est un flexible tool pour suivre de logfiles et execution de commandements. Filtrer, pourvoir de couleur, merge, 'diff-view', etc. http://www.vanheusden.com/multitail/ -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
