From: batouzo <batouzo@gmx.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [3.1.4] mm slub memory corruption in drm_vblank_cleanup
Date: Tue, 13 Dec 2011 21:59:50 +0100 [thread overview]
Message-ID: <jc8ec6$m42$1@dough.gmane.org> (raw)
In-Reply-To: <jc7q4e$qv9$1@dough.gmane.org>
On 12/13/2011 04:14 PM, batouzo wrote:
Should I write to soem other group and/or email developers as well?
Can anyone help debug this bug?
> Allocated in drm_vblank_init+0x139/0x260 [drm] + Freed in
> drm_vblank_cleanup+0x78/0x90 [drm]
> Allocated in drm_vblank_init+0xbe/0x260 [drm] + Freed in
> drm_vblank_cleanup+0x48/0x90 [drm]
next prev parent reply other threads:[~2011-12-13 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 15:14 [3.1.4] mm slub memory corruption in drm_vblank_cleanup batouzo
2011-12-13 20:59 ` batouzo [this message]
2011-12-15 9:28 ` David Rientjes
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='jc8ec6$m42$1@dough.gmane.org' \
--to=batouzo@gmx.com \
--cc=linux-kernel@vger.kernel.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