From: Jiri Slaby <jslaby@suse.cz>
To: stable <stable@vger.kernel.org>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
bskeggs@redhat.com, dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [stable request] fix for nouveau mem corruption [was: WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242]
Date: Wed, 20 Feb 2013 15:47:05 +0100 [thread overview]
Message-ID: <5124E1E9.5060607@suse.cz> (raw)
In-Reply-To: <20130219070744.GA3032@joi.lan>
On 02/19/2013 08:07 AM, Marcin Slusarz wrote:
>>> Crash/warning should be fixed by commit cfd376b6bfccf33782a0748a9c70f7f752f8b869
>>> "drm/nouveau/vm: fix memory corruption when pgt allocation fails".
>>
>> Oh, thanks for the pointer. Could that bug cause real "memory
>> corruption"? As we're hunting one there...
>
> Yes.
>
>> Isn't this a stable-3.7 candidate?
>
> Should have been :/.
Ok, if you have no objections: stable fellows, please consider the
commit above for stable inclusion. As far as I can tell this is only
applicable for 3.7 -- Marcin?
--
js
suse labs
next prev parent reply other threads:[~2013-02-20 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 10:27 WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242 Jiri Slaby
2013-02-18 23:23 ` Marcin Slusarz
2013-02-18 23:43 ` Jiri Slaby
2013-02-19 2:01 ` Page allocation failures (was Re: WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242) Peter Hurley
2013-02-19 7:07 ` WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242 Marcin Slusarz
2013-02-19 22:32 ` Marcin Slusarz
2013-03-13 10:36 ` Jiri Slaby
2013-06-17 8:45 ` Jiri Slaby
2013-02-20 14:47 ` Jiri Slaby [this message]
2013-02-20 18:57 ` [stable request] fix for nouveau mem corruption [was: WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242] Marcin Slusarz
2013-02-20 18:57 ` Marcin Slusarz
2013-02-21 22:06 ` Greg KH
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=5124E1E9.5060607@suse.cz \
--to=jslaby@suse.cz \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.