mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	virtualization@lists.linux-foundation.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/bochs: Fix NULL dereference on atomic_disable helper
Date: Mon, 11 Mar 2019 07:11:59 -0300	[thread overview]
Message-ID: <20190311101159.t6mbzm5sdwuh5muc@smtp.gmail.com> (raw)
In-Reply-To: <20190311062200.4mtel3j5fjxtxrcf@sirius.home.kraxel.org>

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

On 03/11, Gerd Hoffmann wrote:
> On Sun, Mar 10, 2019 at 06:21:50PM -0300, Rodrigo Siqueira wrote:
> > When the subtest basic-plain-flip from IGT project was executed on Bochs
> > driver, the following bug appears:
> > 
> > BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
> 
> >  ? drm_atomic_helper_commit_modeset_disables+0x396/0x3e0 [drm_kms_helper]
> 
> > +static void  bochs_crtc_atomic_disable(struct drm_crtc *crtc,
> > +				       struct drm_crtc_state *old_state)
> > +{
> > +}
> > +
> >  static void bochs_crtc_atomic_flush(struct drm_crtc *crtc,
> >  				    struct drm_crtc_state *old_crtc_state)
> >  {
> > @@ -66,6 +71,7 @@ static const struct drm_crtc_funcs bochs_crtc_funcs = {
> >  static const struct drm_crtc_helper_funcs bochs_helper_funcs = {
> >  	.mode_set_nofb = bochs_crtc_mode_set_nofb,
> >  	.atomic_enable = bochs_crtc_atomic_enable,
> > +	.atomic_disable = bochs_crtc_atomic_disable,
> 
> Shouldn't we make the callback optional instead of adding empty dummy
> functions to drivers?

Hi Gerd,

I agree, and I can work in this issue.
Just one question, should we make atomic_enable optional as well?
 
Thanks for your feedback,
Best Regards
> cheers,
>   Gerd
> 

-- 
Rodrigo Siqueira
https://siqueira.tech
Graduate Student
Department of Computer Science
University of São Paulo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-11 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 21:21 Rodrigo Siqueira
2019-03-11  6:22 ` Gerd Hoffmann
2019-03-11 10:11   ` Rodrigo Siqueira [this message]
2019-03-11 13:07     ` Gerd Hoffmann
2019-03-11 13:23       ` Daniel Vetter
2019-03-11 13:39         ` Gerd Hoffmann
2019-03-11 17:49           ` Rodrigo Siqueira
2019-03-11 18:48             ` Daniel Vetter

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=20190311101159.t6mbzm5sdwuh5muc@smtp.gmail.com \
    --to=rodrigosiqueiramelo@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®