All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: "Alex Deucher"
	<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Alex Deucher" <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
	"Christian König"
	<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
	"Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: don't add files at control minor debugfs directory
Date: Thu, 08 Dec 2016 04:52:58 -0500	[thread overview]
Message-ID: <1665684.nljZfOBslP@segfault> (raw)
In-Reply-To: <65ba1d07-7c50-c0d8-4d1b-bcdc7d447a63-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>

On Tuesday, December 6, 2016 8:59:09 AM EST Christian König wrote:
> Am 06.12.2016 um 02:00 schrieb Michel Dänzer:
> > On 06/12/16 05:07 AM, Alex Deucher wrote:
> >> Since commit 8a357d10043c ("drm: Nerf DRM_CONTROL nodes"), a
> >> struct drm_device's ->control member is always NULL.
> >> 
> >> In the case of CONFIG_DEBUG_FS=y, amdgpu_debugfs_add_files() accesses
> >> ->control->debugfs_root though. This results in the following Oops:
> >> 
> >> [    9.627636] BUG: unable to handle kernel NULL pointer dereference at
> >> 0000000000000018 [    9.628274] IP: amdgpu_debugfs_add_files+0x8d/0x100
> >> [amdgpu]
> >> [    9.628867] PGD 2514c7067
> >> [    9.628876] PUD 2514c8067
> >> [    9.629448] PMD 0
> >> [    9.630026] Oops: 0000 [#1] PREEMPT SMP
> >> [...]
> >> [    9.639906] Call Trace:
> >> [    9.640538]  amdgpu_fence_driver_init+0x1e/0x40 [amdgpu]
> >> [    9.641186]  amdgpu_device_init+0xa6d/0x1410 [amdgpu]
> >> [    9.641900]  ? kmalloc_order_trace+0x2e/0x100
> >> [    9.642587]  amdgpu_driver_load_kms+0x5b/0x200 [amdgpu]
> >> [    9.643355]  drm_dev_register+0xa7/0xd0
> >> [    9.644016]  drm_get_pci_dev+0xde/0x1d0
> >> [    9.644659]  amdgpu_pci_probe+0xbe/0xf0 [amdgpu]
> >> [...]
> >> 
> >> Fix this by omitting the drm_debugfs_create_files() call for the
> >> control minor debugfs directory which is now non-existent anyway.
> >> 
> >> Port of Nicolai Stange's radeon patch to amdgpu.
> >> 
> >> bug: https://bugs.freedesktop.org/show_bug.cgi?id=98915
> > 
> > Not sure about the kernel, but in other projects the convention is
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98915
> > 
> >> Fixes: 8a357d10043c ("drm: Nerf DRM_CONTROL nodes")
> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > 
> > Regardless of the above,
> > 
> > Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
> 
> Reviewed-by: Christian König <christian.koenig@amd.com>.
> 

Worked fine, fixed the issue for me.

Tested-by: Shawn Starr <shawn.starr@rogers.com>

> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx


_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2016-12-08  9:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 20:07 [PATCH] drm/amdgpu: don't add files at control minor debugfs directory Alex Deucher
     [not found] ` <1480968458-2270-1-git-send-email-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2016-12-06  1:00   ` Michel Dänzer
     [not found]     ` <8a8380a1-fb41-e4e9-8c30-7ea075a241ac-otUistvHUpPR7s880joybQ@public.gmane.org>
2016-12-06  7:59       ` Christian König
     [not found]         ` <65ba1d07-7c50-c0d8-4d1b-bcdc7d447a63-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2016-12-08  9:52           ` Shawn Starr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-05  8:48 [PATCH] drm/radeon: " Christian König
2016-12-05 20:30 ` [PATCH] drm/amdgpu: " Nicolai Stange
2016-12-05 20:33   ` Deucher, Alexander
2016-12-05 20:33     ` Deucher, Alexander
2016-12-06  2:01     ` Mike Lothian
2016-12-06  7:17       ` Daniel Vetter
2016-12-06  7:17         ` 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=1665684.nljZfOBslP@segfault \
    --to=shawn.starr-bjeeyj9ojedqt0dzr+alfa@public.gmane.org \
    --cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.