From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755385AbYDBHZO (ORCPT ); Wed, 2 Apr 2008 03:25:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754104AbYDBHZB (ORCPT ); Wed, 2 Apr 2008 03:25:01 -0400 Received: from brick.kernel.dk ([87.55.233.238]:15410 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753563AbYDBHZA (ORCPT ); Wed, 2 Apr 2008 03:25:00 -0400 Date: Wed, 2 Apr 2008 09:24:57 +0200 From: Jens Axboe To: Pekka J Enberg Cc: Peter Zijlstra , Vegard Nossum , Ingo Molnar , Linux Kernel Mailing List , "Paul E. McKenney" Subject: Re: kmemcheck caught read from freed memory (cfq_free_io_context) Message-ID: <20080402072456.GI12774@kernel.dk> References: <19f34abd0804011408v19e13b6cje1ca89a2a471484c@mail.gmail.com> <1207085788.29991.6.camel@lappy> <20080402071709.GC12774@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 02 2008, Pekka J Enberg wrote: > On Wed, 2 Apr 2008, Jens Axboe wrote: > > Good catch, I wonder why it didn't complain in my testing. I've added a > > patch to fix that, please see it here: > > You probably don't have kmemcheck in your kernel ;-) Ehm no, you are right :) -- Jens Axboe