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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Nov 2009 14:30:56 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Jerome Glisse <jglisse@...hat.com> Cc: airlied@...il.com, dri-devel@...ts.sf.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] drm/radeon/kms: Fix oops when set_base is call with no FB On Wed, 4 Nov 2009 20:03:19 +0100 Jerome Glisse <jglisse@...hat.com> wrote: > Just do nothings crct_set_base i call with no FB. > hmpf. It's obvious that you spent hours carefully describing this patch for us. > diff --git a/drivers/gpu/drm/radeon/atombios_crtc.c b/drivers/gpu/drm/radeon/atombios_crtc.c > index c15287a..f5987af 100644 > --- a/drivers/gpu/drm/radeon/atombios_crtc.c > +++ b/drivers/gpu/drm/radeon/atombios_crtc.c > @@ -578,8 +578,11 @@ int atombios_crtc_set_base(struct drm_crtc *crtc, int x, int y, > uint64_t fb_location; > uint32_t fb_format, fb_pitch_pixels, tiling_flags; > > - if (!crtc->fb) > - return -EINVAL; > + /* no fb bound */ > + if (!crtc->fb) { > + DRM_DEBUG("No FB bound\n"); > + return 0; > + } > > radeon_fb = to_radeon_framebuffer(crtc->fb); > > diff --git a/drivers/gpu/drm/radeon/radeon_legacy_crtc.c b/drivers/gpu/drm/radeon/radeon_legacy_crtc.c > index 8d0b7aa..5794364 100644 > --- a/drivers/gpu/drm/radeon/radeon_legacy_crtc.c > +++ b/drivers/gpu/drm/radeon/radeon_legacy_crtc.c > @@ -408,6 +408,11 @@ int radeon_crtc_set_base(struct drm_crtc *crtc, int x, int y, > uint32_t gen_cntl_reg, gen_cntl_val; > > DRM_DEBUG("\n"); > + /* no fb bound */ > + if (!crtc->fb) { > + DRM_DEBUG("No FB bound\n"); > + return 0; > + } > > radeon_fb = to_radeon_framebuffer(crtc->fb); Under which circumstances does this oops occur? What userspace actions? See, curious minds want to know whether this patch is needed in 2.6.33, 2.6.32, 2.6.31.x, 2.6.30,x, etc, etc. Often we rely upon the originator to provide us with enough information to make that decision. You didn't do this. Please always do so. -- 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/
Powered by blists - more mailing lists