linux-kernel - Re: Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0908260949550.9396@p34.internal.lan>
Date:	Wed, 26 Aug 2009 09:50:27 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Christoph Hellwig <hch@...radead.org>
cc:	linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: Re: Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6)



On Mon, 24 Aug 2009, Justin Piszcz wrote:

>
>
> 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@...e.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.
>

Hi Christoph,

So far the uptime is 2 days, if it does not recur in the next 24-48 hours, 
do you recommend I follow up with the linux-crypto folks about this?  It 
appears this could be the cause (no issues, as of yet).

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