linux-kernel - Re: list corruption in the last few days. (block ? crypto ?)

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:	Mon, 8 Aug 2011 14:34:19 +0800
From:	Xiaotian Feng <xtfeng@...il.com>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Jones <davej@...hat.com>,
	Christoph Lameter <cl@...ux.com>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <jaxboe@...ionio.com>
Subject: Re: list corruption in the last few days. (block ? crypto ?)

On Mon, Aug 8, 2011 at 2:16 PM, Pekka Enberg <penberg@...nel.org> wrote:
> On Mon, Aug 8, 2011 at 9:14 AM, Xiaotian Feng <xtfeng@...il.com> wrote:
>> On Mon, Aug 8, 2011 at 1:18 PM, Pekka Enberg <penberg@...nel.org> wrote:
>>> Hi Linus,
>>>
>>> On Sun, Aug 7, 2011 at 11:58 AM, Pekka Enberg <penberg@...nel.org> wrote:
>>>>>
>>>>> Christoph, I've been reading the code and spotted two potential issues in
>>>>> __slab_free(). The first one seems like an off-by-one where our
>>>>> comparison
>>>>> in deactivate_slab() doesn't match __slab_free.
>>>>>
>>>>> The other one is remove_full() call in __slab_free() that can get called
>>>>> even if cache debugging is not enabled.
>>>>>
>>>>> Hmm?
>>>
>>> On Sun, 7 Aug 2011, Linus Torvalds wrote:
>>>>
>>>> I'd like to do -rc1 today, regardless of whether this fixes things or
>>>> not (-rc1 is already a few days delayed).
>>>>
>>>> The patch seems to be a good fix, and a likely candidate for the
>>>> corruption. Commit log and sign-off? I assume you've given it some
>>>> testing, even if you couldn't reproduce the original issue?
>>>
>>> No, I haven't tested the patch myself but here's one in proper format in
>>> case someone wants to test it.
>>
>> I applied it and I'm still seeing the corruption warning start from this :(
>
> Thanks for testing. Can you share your .config, please?

Attached, thanks.

>

Download attachment "myconfig" of type "application/octet-stream" (135759 bytes)