linux-kernel - Re: Memory corruption warnings triggered by repeated slabinfo -v

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] [day] [month] [year] [list]

Date:	Sat, 17 Dec 2011 21:55:40 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Alex Villacís Lasso <a_villacis@...osanto.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: Memory corruption warnings triggered by repeated slabinfo -v

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.



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