mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6)
Date: Mon, 24 Aug 2009 07:04:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0908240704130.9427@p34.internal.lan> (raw)
In-Reply-To: <20090823224504.GA19942@infradead.org>



On Sun, 23 Aug 2009, Christoph Hellwig wrote:

> Ok, let's see where errors could happen then.
>
> There are four theoretical possibilities:
>
> (a) XFS
> (b) loop driver
> (c) crypto loop code
> (d) block layer
>
> Or combinations thereof.
>
> I would take (a) and (d) as more unlikely as they tend to get used much
> more and I would have heard more bug reports already.
>
> The cryptoloop code hasn't changed at all since 2.6.29.
>
> The loop code howver has a very interesting commit just after 2.6.39:
>
> commit 68db1961bbf4e16c220ccec4a780e966bc1fece3
> Author: Nikanth Karthikesan <knikanth@suse.de>
> Date:   Tue Mar 24 12:29:54 2009 +0100
>
>    loop: support barrier writes
>
> Can you try reverting this one (it cleanly reverse-applies against
> 2.6.30 and current mainline) and see if that makes a difference?
>

Hello Christoph,

# patch -p1 -R < ../unpatch.patch
patching file drivers/block/loop.c
Hunk #1 succeeded at 473 (offset -1 lines).
Hunk #2 succeeded at 804 (offset -22 lines).
#

Patched, we'll see if the problem recurs.. thanks!

Justin.

  reply	other threads:[~2009-08-24 11:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  8:39 Kernel 2.6.30.4 XFS(..?) regression Justin Piszcz
2009-08-08 19:31 ` Felix Blyakher
2009-08-09 10:09   ` Justin Piszcz
2009-08-11 10:58     ` Kernel 2.6.30.4 XFS(..?) regression (happened again) Justin Piszcz
2009-08-16  2:23       ` Christoph Hellwig
2009-08-17 14:25         ` Justin Piszcz
2009-08-22 10:27           ` Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6) Justin Piszcz
2009-08-22 14:25             ` Christoph Hellwig
2009-08-22 14:45               ` Justin Piszcz
2009-08-22 20:15                 ` Christoph Hellwig
2009-08-22 20:46                   ` Justin Piszcz
2009-08-22 20:55                     ` Christoph Hellwig
2009-08-22 21:01                       ` Justin Piszcz
2009-08-23 22:45                         ` Christoph Hellwig
2009-08-24 11:04                           ` Justin Piszcz [this message]
2009-08-26 13:50                             ` Justin Piszcz
2009-08-26 18:02                               ` Kernel 2.6.30.4 loop(..?) " Christoph Hellwig
2009-08-26 21:19                                 ` Justin Piszcz
2009-08-26 21:27                                   ` Christoph Hellwig
2009-08-26 21:31                                     ` Justin Piszcz
2009-08-28 11:23                                       ` Justin Piszcz
2009-08-28 16:55                                         ` Christoph Hellwig
2009-09-02 11:45                                         ` Justin Piszcz

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=alpine.DEB.2.00.0908240704130.9427@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®