From: Jakob Bornecrantz <jakob@vmware.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: airlied@linux.ie, airlied@redhat.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
joe Perches <joe@perches.com>, Ryan Mallon <rmallon@gmail.com>
Subject: Re: [RFC PATCH] vmwgfx: Fix assignment in vmw_framebuffer_create_handle
Date: Fri, 27 Jan 2012 06:24:53 -0800 (PST) [thread overview]
Message-ID: <1345211595.178155.1327674293610.JavaMail.root@zimbra-prod-mbox-2.vmware.com> (raw)
In-Reply-To: <4F22B02F.2010502@vmware.com>
I was asking around and this seems to only be used by X when it
starts and we want to preserve the contents of the screen. That
feature is implemented by the X driver. So we need to figure how we
want to solve it.
Either way this fix should probably go into this RC series, not
sure if we need to send this to stable, since we are not leaking
data to userspace (check drm_mode_getfb), but we might as well.
Reviewed-by: Jakob Bornecrantz <jakob@vmware.com>
Cheers, Jakob.
----- Original Message -----
> Ryan,
>
> Thanks for pointing this out. Unfortunately there seems to be two
> bugs here, the one you pointed out and the fact that we set the handle
> to zero, when it probably should be set to struct
> vmw_framebuffer::user_handle.
>
> Jakob, can you comment on this?
>
> /Thomas
>
> On 01/27/2012 07:25 AM, Ryan Mallon wrote:
> > The assignment of handle in vmw_framebuffer_create_handle doesn't
> > actually do anything useful and is incorrectly assigning an integer
> > value to a pointer argument. It appears that this is a typo and
> > should
> > be dereferencing handle rather than assigning to it directly.
> >
> > Signed-off-by: Ryan Mallon<rmallon@gmail.com>
> > ---
> >
> > diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > index 0af6ebd..b66ef0e 100644
> > --- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > @@ -378,7 +378,7 @@ int vmw_framebuffer_create_handle(struct
> > drm_framebuffer *fb,
> > unsigned int *handle)
> > {
> > if (handle)
> > - handle = 0;
> > + *handle = 0;
> >
> > return 0;
> > }
> >
>
>
next prev parent reply other threads:[~2012-01-27 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 6:25 Ryan Mallon
2012-01-27 14:09 ` Thomas Hellstrom
2012-01-27 14:24 ` Jakob Bornecrantz [this message]
2012-01-27 14:28 ` Thomas Hellstrom
2012-01-27 14:41 ` Jakob Bornecrantz
2012-01-27 14:54 ` Thomas Hellstrom
2012-01-27 15:01 ` Jakob Bornecrantz
2012-01-27 15:32 ` Thomas Hellstrom
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=1345211595.178155.1327674293610.JavaMail.root@zimbra-prod-mbox-2.vmware.com \
--to=jakob@vmware.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.com \
--cc=thellstrom@vmware.com \
/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
Powered by JetHome