linux-kernel - Re: memory corruption after "Fix race when checking i

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: <20140209020933.GA23163@fieldses.org>
Date:	Sat, 8 Feb 2014 21:09:33 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Steven Whitehouse <swhiteho@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-nfs@...r.kernel.org
Subject: Re: memory corruption after "Fix race when checking i_size on direct
 i/o read"

On Sat, Feb 08, 2014 at 03:45:22PM -0500, bfields wrote:
> I'm getting warnings about corruption of the kmalloc-32 slab on an nfs
> server while running some regression tests.
> 
> A bisect lands on 9fe55eea7e4b444bafc42fa0000cc2d1d2847275 "Fix race
> when checking i_size on direct i/o read".  Is there any known problem
> here?
> 
> It doesn't reproduce immediately and it's possible I could have made a
> mistake on the bisect.

Argh, apologies, yes--I'm able to reproduce the corruption before that
commit.  I'll keep looking....

--b.
--
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/