From: Dave Chinner <david@fromorbit.com>
To: Brian May <brian@vpac.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-fsdevel@vger.kernel.org
Subject: Re: open sleeps
Date: Fri, 20 Jun 2008 16:45:29 +1000 [thread overview]
Message-ID: <20080620064529.GA29319@disturbed> (raw)
In-Reply-To: <485B03DA.5070501@vpac.org>
On Fri, Jun 20, 2008 at 11:11:54AM +1000, Brian May wrote:
> Brian May wrote:
>> Stephen Rothwell wrote:
>>> Its what samba calls an oplock. Its like a kernel file lock but it
>>> blocks opens and notifies the holder (who is supposed to clean up and
>>> release the lease). If the lease is not released in 45 seconds (by
>>> default) then the kernel assumes that the holder is broken and breaks
>>> the
>>> lease and allows the open to proceed.
>>>
>> Ok, so I guess it is most likely Samba's fault then. Most likely this
>> is the only application that uses leases/oplocks on this computer
>> anyway. I will keep investigating...
> Maybe I spoke too soon when I ruled XFS out :-(.
....
> hq:~# echo t > /proc/sysrq-trigger
> Gives a stack trace of:
>
> Jun 20 10:54:37 hq kernel: Call Trace:
>
> Jun 20 10:54:37 hq kernel: [<c0125380>] lock_timer_base+0x15/0x2f
> Jun 20 10:54:37 hq kernel: [<c027f960>] schedule_timeout+0x71/0x8c
> Jun 20 10:54:37 hq kernel: [<c0124a81>] process_timeout+0x0/0x5
> Jun 20 10:54:37 hq kernel: [<c016a115>] do_select+0x37a/0x3d4
> Jun 20 10:54:37 hq kernel: [<c016a677>] __pollwait+0x0/0xb2
> Jun 20 10:54:37 hq kernel: [<c0117778>] default_wake_function+0x0/0xc
> Jun 20 10:54:37 hq kernel: [<c0117778>] default_wake_function+0x0/0xc
> Jun 20 10:54:37 hq kernel: [<f88e998f>] e1000_xmit_frame+0x928/0x958 [e1000]
> Jun 20 10:54:37 hq kernel: [<c0121c24>] tasklet_action+0x55/0xaf
> Jun 20 10:54:37 hq kernel: [<c022950a>] dev_hard_start_xmit+0x19a/0x1f0
> Jun 20 10:54:37 hq kernel: [<f8ae3e6d>] xfs_iext_bno_to_ext+0xd8/0x191 [xfs]
> Jun 20 10:54:37 hq kernel: [<f8ac7aec>] xfs_bmap_search_multi_extents+0xa8/0xc5 [xfs]
> Jun 20 10:54:37 hq kernel: [<f8ac7b52>] xfs_bmap_search_extents+0x49/0xbe [xfs]
> Jun 20 10:54:37 hq kernel: [<f8ac7e35>] xfs_bmapi+0x26e/0x20ce [xfs]
> Jun 20 10:54:37 hq kernel: [<f8ac7e35>] xfs_bmapi+0x26e/0x20ce [xfs]
> Jun 20 10:54:37 hq kernel: [<c02547e4>] tcp_transmit_skb+0x604/0x632
> Jun 20 10:54:37 hq kernel: [<c02560d3>] __tcp_push_pending_frames+0x6a2/0x758
> Jun 20 10:54:37 hq kernel: [<c016d84e>] __d_lookup+0x98/0xdb
> Jun 20 10:54:37 hq kernel: [<c016d84e>] __d_lookup+0x98/0xdb
> Jun 20 10:54:37 hq kernel: [<c0165370>] do_lookup+0x4f/0x135
> Jun 20 10:54:37 hq kernel: [<c016dbc4>] dput+0x1a/0x11b
> Jun 20 10:54:37 hq kernel: [<c0167312>] __link_path_walk+0xbe4/0xd1d
> Jun 20 10:54:37 hq kernel: [<c016a3fb>] core_sys_select+0x28c/0x2a9
> Jun 20 10:54:37 hq kernel: [<c01674fe>] link_path_walk+0xb3/0xbd
> Jun 20 10:54:37 hq kernel: [<f8afbea1>] xfs_inactive_free_eofblocks+0xdf/0x23f [xfs]
> Jun 20 10:54:37 hq kernel: [<c016785d>] do_path_lookup+0x20a/0x225
> Jun 20 10:54:37 hq kernel: [<f8b07de5>] xfs_vn_getattr+0x27/0x2f [xfs]
> Jun 20 10:54:37 hq kernel: [<c0161b28>] cp_new_stat64+0xfd/0x10f
> Jun 20 10:54:37 hq kernel: [<c016a9c1>] sys_select+0x9f/0x182
> Jun 20 10:54:37 hq kernel: [<c0102c11>] sysenter_past_esp+0x56/0x79
This is just the stupid (broken) ia32 stack tracing - it outputs every
single object it sees in the stack that may be function call. Hence
you see some stuff that is from past stack traversals. I'd say this
is sleeping in a select() call, not doing anything related to
xfs or networking....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-20 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 23:14 open sleeps Brian May
2008-06-19 23:58 ` Stephen Rothwell
2008-06-20 0:07 ` Brian May
2008-06-20 0:20 ` Stephen Rothwell
2008-06-20 0:50 ` Brian May
2008-06-20 1:11 ` Brian May
2008-06-20 6:45 ` Dave Chinner [this message]
2008-06-26 6:30 ` Brian May
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=20080620064529.GA29319@disturbed \
--to=david@fromorbit.com \
--cc=brian@vpac.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).