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]

Date:	Sat, 22 Aug 2009 16:46:52 -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 Sat, 22 Aug 2009, Christoph Hellwig wrote:

> On Sat, Aug 22, 2009 at 10:45:13AM -0400, Justin Piszcz wrote:
>>> Yes, entirely possible.   All the crypto loop / dm implementation used
>>> to have a tendency to never complete I/O once in a while, although that
>>> didn't happen anymore recently.
>>
>> Ok,
>>
>> What is the best way to debug the issue? git bi-sects between 2.6.29.x
>> and 2.6.31-rc6? or?
>
> Well, that would be a good way to find it.  But I'm personally not
> interested in spending much time on debugging a problem if it only
> happens with fishy out of tree modules.
>

.. No out of tree modules are used ..

Here is the kernel config used:
http://home.comcast.net/~jpiszcz/20090822/config.txt

After 24hrs of various tar-like read/write/verify I/O, the error usually 
recurs.

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/