From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Alex Villacís Lasso" <a_villacis@palosanto.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Memory corruption warnings triggered by repeated slabinfo -v
Date: Sat, 17 Dec 2011 21:55:40 +0100 [thread overview]
Message-ID: <1324155340.3323.23.camel@edumazet-laptop> (raw)
In-Reply-To: <4EECF64B.1020409@palosanto.com>
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.
prev parent reply other threads:[~2011-12-17 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 2:14 Alex Villacís Lasso
2011-12-17 3:28 ` Eric Dumazet
2011-12-17 20:06 ` Alex Villacís Lasso
2011-12-17 20:55 ` Eric Dumazet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1324155340.3323.23.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=a_villacis@palosanto.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®