All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS read hangs in 3.1-rc10
Date: Wed, 26 Oct 2011 07:25:21 -0400	[thread overview]
Message-ID: <20111026112521.GA10432@infradead.org> (raw)
In-Reply-To: <20111025200748.GA25043@hostway.ca>

On Tue, Oct 25, 2011 at 01:07:48PM -0700, Simon Kirby wrote:
> This patch seems to work, at least on an SSD box. No more hung task
> warnings, and everything appears normal.
> 
> Do we know what caused this regression and/or how to fix it without the
> big hammer, or do we need to break it down further?

I have an idea and will send you a refined patch soon.  I'm at a
conference until tomorrow, so you'll probably have to wait another day
or two for it.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS read hangs in 3.1-rc10
Date: Wed, 26 Oct 2011 07:25:21 -0400	[thread overview]
Message-ID: <20111026112521.GA10432@infradead.org> (raw)
In-Reply-To: <20111025200748.GA25043@hostway.ca>

On Tue, Oct 25, 2011 at 01:07:48PM -0700, Simon Kirby wrote:
> This patch seems to work, at least on an SSD box. No more hung task
> warnings, and everything appears normal.
> 
> Do we know what caused this regression and/or how to fix it without the
> big hammer, or do we need to break it down further?

I have an idea and will send you a refined patch soon.  I'm at a
conference until tomorrow, so you'll probably have to wait another day
or two for it.

  reply	other threads:[~2011-10-26 11:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 22:42 XFS read hangs in 3.1-rc10 Simon Kirby
2011-10-20 22:42 ` Simon Kirby
2011-10-21 13:22 ` Christoph Hellwig
2011-10-21 13:22   ` Christoph Hellwig
2011-10-21 20:28   ` Simon Kirby
2011-10-21 20:28     ` Simon Kirby
2011-10-24  8:22     ` Christoph Hellwig
2011-10-24  8:22       ` Christoph Hellwig
2011-10-25 20:07       ` Simon Kirby
2011-10-25 20:07         ` Simon Kirby
2011-10-26 11:25         ` Christoph Hellwig [this message]
2011-10-26 11:25           ` Christoph Hellwig
2011-11-04 21:03           ` Christoph Hellwig
2011-11-04 21:03             ` Christoph Hellwig
2011-11-16 19:56             ` Simon Kirby
2011-11-16 19:56               ` Simon Kirby
2011-11-20 15:32               ` Christoph Hellwig
2011-11-20 15:32                 ` Christoph Hellwig
2011-11-28 19:05                 ` Simon Kirby
2011-11-28 19:05                   ` Simon Kirby
2011-11-28 19:55                   ` Christoph Hellwig
2011-11-28 19:55                     ` Christoph Hellwig
2011-11-28 21:01                     ` Ben Myers
2011-11-28 21:01                       ` Ben Myers
2011-10-21 20:29   ` Markus Trippelsdorf
2011-10-21 20:29     ` Markus Trippelsdorf

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=20111026112521.GA10432@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sim@hostway.ca \
    --cc=xfs@oss.sgi.com \
    /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.