From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752500Ab1LQUzs (ORCPT ); Sat, 17 Dec 2011 15:55:48 -0500 Received: from mail-wi0-f174.google.com ([209.85.212.174]:56878 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752265Ab1LQUzp (ORCPT ); Sat, 17 Dec 2011 15:55:45 -0500 Message-ID: <1324155340.3323.23.camel@edumazet-laptop> Subject: Re: Memory corruption warnings triggered by repeated slabinfo -v From: Eric Dumazet To: Alex =?ISO-8859-1?Q?Villac=EDs?= Lasso Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org Date: Sat, 17 Dec 2011 21:55:40 +0100 In-Reply-To: <4EECF64B.1020409@palosanto.com> References: <4EEBFAF3.60609@palosanto.com> <1324092514.2621.49.camel@edumazet-laptop> <4EECF64B.1020409@palosanto.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.1- Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le samedi 17 décembre 2011 à 15:06 -0500, Alex Villacís Lasso a écrit : > El 16/12/11 22:28, Eric Dumazet escribió: > > Le vendredi 16 décembre 2011 à 21:14 -0500, Alex Villacís Lasso a > > écrit : > >> I am running Fedora 16 x86_64 and testing vanilla kernel 3.2-rc5. I > >> wanted to test the slabinfo program, so I wrote a small shell script > >> slabinfo-forever.sh (attached) that invokes slabinfo -v every 3 seconds. > >> Just by doing this, I was able to trigger several memory validation > >> warnings, attached in this message. The reason I wanted to test slabinfo > >> is because back when I was running Fedora 14, I had some video issues > >> that seemed consistent with memory corruption. I tried to submit a > >> kernel bug at https://bugzilla.kernel.org/show_bug.cgi?id=42312 just > >> before the kernel.org hack issue, but bugzilla.kernel.org never came up > >> after that. > > Problem is known and fixes were submitted. > > > > > Still happening in 3.2-rc6. The dmesg output is attached. > > What are the git commits of the fixes? Are they scheduled to go into 3.2 > stable? Fixes were submitted but not yet accepted in mainline.