public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@redhat.com>
To: "Alexander Y. Fomichev" <git.user@gmail.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	Robert Noland <rnoland@2hip.net>,
	Matt Turner <mattst88@gmail.com>,
	Jerome Glisse <jglisse@redhat.com>,
	akpm@linux-foundation.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: drivers/gpu/drm/radeon/r600_blit.c: fix possible NULL pointer  derefernce
Date: Wed, 21 Jul 2010 10:30:43 +1000	[thread overview]
Message-ID: <1279672243.337.10.camel@clockmaker-el6> (raw)
In-Reply-To: <AANLkTimNpacSqjgNN-bNdK-vOwep5LEprE_PvaEbjuDj@mail.gmail.com>

On Wed, 2010-07-21 at 01:07 +0400, Alexander Y. Fomichev wrote:
> On Wed, Jul 21, 2010 at 1:00 AM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Tue, Jul 20, 2010 at 4:13 PM, Alexander Y. Fomichev
> > <git.user@gmail.com> wrote:
> >> On Tue, Jul 20, 2010 at 9:37 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> >>> On Mon, Jul 19, 2010 at 5:42 PM, Alexander Y. Fomichev
> >>> <git.user@gmail.com> wrote:
> >>>> This patch fix possible NULL pointer dereference when
> >>>> r600_prepare_blit_copy tries to fill dev_priv->blit_vb->file_priv
> >>>> without check of dev_priv->blit_vb. dev_priv->blit_vb should be
> >>>> filled by r600_nomm_get_vb but latest can fail with EAGAIN.
> >>>> Addresses: https://bugzilla.kernel.org/show_bug.cgi?id=16375
> >>>>
> >>>> ---
> >>>>  drivers/gpu/drm/radeon/r600_blit.c |    2 ++
> >>>>  1 files changed, 2 insertions(+), 0 deletions(-)
> >>>>
> >>>> diff --git a/drivers/gpu/drm/radeon/r600_blit.c b/drivers/gpu/drm/radeon/r600_blit.c
> >>>> index f4fb88e..0df4a2b 100644
> >>>> --- a/drivers/gpu/drm/radeon/r600_blit.c
> >>>> +++ b/drivers/gpu/drm/radeon/r600_blit.c
> >>>> @@ -541,6 +541,8 @@ r600_prepare_blit_copy(struct drm_device *dev, struct drm_file *file_priv)
> >>>>        DRM_DEBUG("\n");
> >>>>
> >>>>        r600_nomm_get_vb(dev);
> >>>> +       if (!dev_priv->blit_vb)
> >>>> +               return;
> >>>
> >>> r600_prepare_blit_copy returns an int so something like this would be better:
> >>> --- a/drivers/gpu/drm/radeon/r600_blit.c
> >>> +++ b/drivers/gpu/drm/radeon/r600_blit.c
> >>> @@ -539,8 +539,10 @@ r600_prepare_blit_copy(struct drm_device *dev,
> >>> struct drm_file *file_priv)
> >>>  {
> >>>        drm_radeon_private_t *dev_priv = dev->dev_private;
> >>>        DRM_DEBUG("\n");
> >>> +       int ret = r600_nomm_get_vb(dev);
> >>>
> >>> -       r600_nomm_get_vb(dev);
> >>> +       if (ret)
> >>> +               return ret;
> >>>
> >>>        dev_priv->blit_vb->file_priv = file_priv;
> >>>
> >>>
> >>> Alex
> >>>
> >>>>
> >>>>        dev_priv->blit_vb->file_priv = file_priv;
> >>>>
> >>>> --
> >>>> 1.7.1.1
> >>>>
> >>>
> >>
> >> i haven't any preferneces, the only thing is - it would be logical
> >> to have every check in common style, so other cases
> >> (r600_blit_copy, r600_blit_swap) should be fixed, nop?
> >
> > Those are void functions so there's nothing to return.
> 
> i mean both of them call r600_nomm_get_vb and both of them
> check if (!dev_priv->blit_vb), not return  value.I mean would be
> logical to check it the same way everytime r600_nomm_get_vb
> gets called.

I'm going to go with Alex's patch, as none of the other callsites return
an error, and your patch doesn't return value from a function which has
a int return type, causing a warning.

Dave.




      parent reply	other threads:[~2010-07-21  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 21:42 drivers/gpu/drm/radeon/r600_blit.c: fix possible NULL pointer derefernce Alexander Y. Fomichev
2010-07-20 17:37 ` Alex Deucher
2010-07-20 20:13   ` Alexander Y. Fomichev
2010-07-20 21:00     ` Alex Deucher
2010-07-20 21:07       ` Alexander Y. Fomichev
2010-07-20 21:29         ` Alex Deucher
2010-07-21  7:06           ` Alexander Y. Fomichev
2010-07-21  0:30         ` Dave Airlie [this message]

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=1279672243.337.10.camel@clockmaker-el6 \
    --to=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=git.user@gmail.com \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=rnoland@2hip.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