From: Chris Mason <chris.mason@oracle.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: task imap:2958 blocked for more than 120 seconds
Date: Wed, 13 Jan 2010 20:07:09 -0500 [thread overview]
Message-ID: <20100114010709.GD3428@think> (raw)
In-Reply-To: <201001132337.34909.johannes.hirte@fem.tu-ilmenau.de>
On Wed, Jan 13, 2010 at 11:37:33PM +0100, Johannes Hirte wrote:
> Am Sonntag 10 Januar 2010 21:19:26 schrieb Chris Mason:
> > On Sun, Jan 10, 2010 at 09:05:46PM +0100, Johannes Hirte wrote:
> > > I've observed this hanging task now several times. Not sure when this
> > > started, but 2.6.32 is affected too, IIRC. I don't have a test pattern
> > > for this. Dovecot imap triggers this from time to time. I've enabled
> > > CONFIG_DETECT_HUNG_TASK now
> >
> > > and got this two tasks which hang:
> > You're stuck on a read, could you please do a sysrq-w when this happens?
>
> Will do so when it happens again.
No need, I reread the trace, you're stuck in copy_from_user and probably
hitting a deadlock in the btrfs page faulting path. This is pretty
rare, but I'll put it into the queue to fix up.
>
> > Also, do you eventually recover or are you stuck forever?
>
> I didn't wait too long when it happened, so I'm not sure. The longest time
> I've waited was 20-30min, until reboot without recover. So either it's stuck
> forever or it takes really long to recover.
>
> And one question I have: How do you identify a read in this call trace?
Lock page followed by sync page is usually for reading.
-chris
next prev parent reply other threads:[~2010-01-14 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 20:05 task imap:2958 blocked for more than 120 seconds Johannes Hirte
2010-01-10 20:19 ` Chris Mason
2010-01-13 22:37 ` Johannes Hirte
2010-01-14 1:07 ` Chris Mason [this message]
2010-01-11 7:34 ` Adrian von Bidder
2010-01-11 8:45 ` Adrian von Bidder
2010-01-14 1:08 ` Chris Mason
2010-01-14 7:03 ` Adrian von Bidder
2010-03-07 15:52 ` Johannes Hirte
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=20100114010709.GD3428@think \
--to=chris.mason@oracle.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.