From: "J. Bruce Fields" Subject: Re: memory corruption after "Fix race when checking i_size on direct i/o read" Date: Sat, 8 Feb 2014 21:09:33 -0500 Message-ID: <20140209020933.GA23163@fieldses.org> References: <20140208204522.GG8801@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steven Whitehouse Return-path: Content-Disposition: inline In-Reply-To: <20140208204522.GG8801-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org 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-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html