From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16375] New: missing blit_vb check in r600_prepare_blit_copy
Date: Mon, 12 Jul 2010 20:56:51 GMT [thread overview]
Message-ID: <bug-16375-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16375
Summary: missing blit_vb check in r600_prepare_blit_copy
Product: Drivers
Version: 2.5
Kernel Version: 2.6.35-rc4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: git.user@gmail.com
Regression: No
r600_prepare_blit_copy issing check of dev_priv->blit_vb to be filled by
r600_nomm_get_vb. r600_nomm_get_vb can fail and return EAGAIN and we'll see a
NULL pointer dereference.
fix:
--- git/linux-2.6/drivers/gpu/drm/radeon/r600_blit.c 2010-03-09
23:26:42.601820012 +0300
+++ linux-2.6.35-rc4/drivers/gpu/drm/radeon/r600_blit.c 2010-07-12
23:55:43.246560111 +0400
@@ -541,6 +541,8 @@ r600_prepare_blit_copy(struct drm_device
DRM_DEBUG("\n");
r600_nomm_get_vb(dev);
+ if (!dev_priv->blit_vb)
+ return;
dev_priv->blit_vb->file_priv = file_priv;
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--
next reply other threads:[~2010-07-12 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 20:56 bugzilla-daemon [this message]
2010-07-15 18:41 ` [Bug 16375] missing blit_vb check in r600_prepare_blit_copy bugzilla-daemon
2010-07-20 9:41 ` bugzilla-daemon
2010-07-22 3:20 ` bugzilla-daemon
2012-08-09 14:24 ` bugzilla-daemon
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=bug-16375-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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