linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Airlie <airlied@redhat.com>
To: Kim Phillips <kim.phillips@amd.com>
Cc: Ainux <ainux.wang@gmail.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	airlied <airlied@linux.ie>, "Vetter, Daniel" <daniel@ffwll.ch>,
	sterlingteng@gmail.com, chenhuacai@kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: KASAN: use-after-free in enqueue_timer+0x4f/0x1e0
Date: Tue, 12 Oct 2021 11:48:24 +1000	[thread overview]
Message-ID: <CAMwc25o9wSPd4PgS56j7GApcFYE=ZY9LHpiFvtE6RVgdQKzBFA@mail.gmail.com> (raw)
In-Reply-To: <a6d2d16c-173f-d49b-ec54-defd6be2bb0c@amd.com>

On Tue, Oct 12, 2021 at 2:07 AM Kim Phillips <kim.phillips@amd.com> wrote:
>
> Hi,
>
> On 10/5/21 1:10 PM, Kim Phillips wrote:
> > Hi, I occasionally see the below trace with Linus' master on an
> > AMD Milan system:
> >
> > [   25.657322] BUG: kernel NULL pointer dereference, address: 0000000000000000
> > [   25.665097] #PF: supervisor instruction fetch in kernel mode
> > [   25.671448] #PF: error_code(0x0010) - not-present page
> <snip>
> > That bisection led to this commit:
> >
> > commit aae74ff9caa8de9a45ae2e46068c417817392a26
> > Author: Ainux <ainux.wang@gmail.com>
> > Date:   Wed May 26 19:15:15 2021 +0800
> >      drm/ast: Add detect function support
> <snip>
> > I confirmed that if I revert it from v5.15-rc4 (after reverting
> > its dependent 572994bf18ff "drm/ast: Zero is missing in detect
> > function"), the problem goes away.
> >
> > Full .config, dmesg attached.
> >
> > I can test any possible fixes...
>
>
> Ping - if no fixes are in the works, can the offending commit(s)
> be reverted?

tzimmermann?

Dave.


      reply	other threads:[~2021-10-12  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 18:10 BUG: KASAN: use-after-free in enqueue_timer+0x4f/0x1e0 Kim Phillips
2021-10-11 16:07 ` Kim Phillips
2021-10-12  1:48   ` David 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='CAMwc25o9wSPd4PgS56j7GApcFYE=ZY9LHpiFvtE6RVgdQKzBFA@mail.gmail.com' \
    --to=airlied@redhat.com \
    --cc=ainux.wang@gmail.com \
    --cc=airlied@linux.ie \
    --cc=chenhuacai@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kim.phillips@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sterlingteng@gmail.com \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).