From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: [Bug #13949] Cryptoloop stuck I/O issue on partition or loopback device
Date: Tue, 8 Sep 2009 21:05:13 +0200
User-Agent: KMail/1.12.1 (Linux/2.6.31-rc9-rjw; KDE/4.3.1; x86_64; ; )
Cc: Christoph Hellwig <hch@infradead.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Kernel Testers List <kernel-testers@vger.kernel.org>,
       Felix Blyakher <felixb@sgi.com>
References: <aIL9jMAYJnG.A.WjH.M3BpKB@chimera> <20090907152553.GA21768@infradead.org> <alpine.DEB.2.00.0909081029050.7636@p34.internal.lan>
In-Reply-To: <alpine.DEB.2.00.0909081029050.7636@p34.internal.lan>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200909082105.13124.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1065
Lines: 28

On Tuesday 08 September 2009, Justin Piszcz wrote:
> 
> On Mon, 7 Sep 2009, Christoph Hellwig wrote:
> 
> > On Sun, Sep 06, 2009 at 08:11:51PM +0200, Rafael J. Wysocki wrote:
> >> This message has been generated automatically as a part of a report
> >> of regressions introduced between 2.6.29 and 2.6.30.
> >>
> >> The following bug entry is on the current list of known regressions
> >> introduced between 2.6.29 and 2.6.30.  Please verify if it still should
> >> be listed and let me know (either way).
> >
> > While this still isn't fixed it has been tracked down to a regression
> > in the loop driver.  Care to adjust the subject?
> >
> 
> Unsure how to edit on the kernel bugtracker but updating this thread to 
> correct the subject.

I've changed the subject and moved the bug to I/O & storage.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/