All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Philip" <Philip.Yang-5C7GfCeVMHo@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
	"Jérôme Glisse" <jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org"
	<linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: KASAN caught amdgpu / HMM use-after-free
Date: Wed, 27 Feb 2019 17:14:04 +0000	[thread overview]
Message-ID: <83fde7eb-abab-e770-efd5-89bc9c39fdff@amd.com> (raw)
In-Reply-To: <e8466985-a66b-468b-5fff-6e743180da67-otUistvHUpPR7s880joybQ@public.gmane.org>

Hi Michel,

Yes, I found the same issue and the bug has been fixed by Jerome:

876b462120aa mm/hmm: use reference counting for HMM struct

The fix is on hmm-for-5.1 branch, I cherry-pick it into my local branch 
to workaround the issue.

Regards,
Philip

On 2019-02-27 12:02 p.m., Michel Dänzer wrote:
> 
> See the attached dmesg excerpt. I've hit this a few times running piglit
> with amd-staging-drm-next, first on February 22nd.
> 
> The memory was freed after calling hmm_mirror_unregister in
> amdgpu_mn_destroy.
> 
> 
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Yang, Philip" <Philip.Yang@amd.com>
To: "Michel Dänzer" <michel@daenzer.net>,
	"Jérôme Glisse" <jglisse@redhat.com>
Cc: "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: KASAN caught amdgpu / HMM use-after-free
Date: Wed, 27 Feb 2019 17:14:04 +0000	[thread overview]
Message-ID: <83fde7eb-abab-e770-efd5-89bc9c39fdff@amd.com> (raw)
In-Reply-To: <e8466985-a66b-468b-5fff-6e743180da67@daenzer.net>

Hi Michel,

Yes, I found the same issue and the bug has been fixed by Jerome:

876b462120aa mm/hmm: use reference counting for HMM struct

The fix is on hmm-for-5.1 branch, I cherry-pick it into my local branch 
to workaround the issue.

Regards,
Philip

On 2019-02-27 12:02 p.m., Michel Dänzer wrote:
> 
> See the attached dmesg excerpt. I've hit this a few times running piglit
> with amd-staging-drm-next, first on February 22nd.
> 
> The memory was freed after calling hmm_mirror_unregister in
> amdgpu_mn_destroy.
> 
> 

  parent reply	other threads:[~2019-02-27 17:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 17:02 KASAN caught amdgpu / HMM use-after-free Michel Dänzer
2019-02-27 17:02 ` Michel Dänzer
     [not found] ` <e8466985-a66b-468b-5fff-6e743180da67-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-02-27 17:14   ` Yang, Philip [this message]
2019-02-27 17:14     ` Yang, Philip
     [not found]     ` <83fde7eb-abab-e770-efd5-89bc9c39fdff-5C7GfCeVMHo@public.gmane.org>
2019-02-27 17:33       ` Michel Dänzer
2019-02-27 17:33         ` Michel Dänzer
     [not found]         ` <c26fa310-38d1-acba-cf82-bc6dc2f782c0-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-02-27 18:05           ` Yang, Philip
2019-02-27 18:05             ` Yang, Philip
     [not found]             ` <35d7e134-6eef-9732-8ebf-83256e40eb65-5C7GfCeVMHo@public.gmane.org>
2019-02-27 18:32               ` Deucher, Alexander
2019-02-27 18:32                 ` Deucher, Alexander
     [not found]                 ` <BN6PR12MB18090BDFE1DD800785C5ED76F7740-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-02-27 18:48                   ` Yang, Philip
2019-02-27 18:48                     ` Yang, Philip
     [not found]                     ` <b81bd33a-0041-392e-2c85-19036fc1c91d-5C7GfCeVMHo@public.gmane.org>
2019-02-28 11:51                       ` Michel Dänzer
     [not found]                         ` <f26e40c8-d981-03ca-839a-6f2340a29b97-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-02-28 15:29                           ` Yang, Philip
2019-02-27 17:24   ` Jerome Glisse
2019-02-27 17:24     ` Jerome Glisse

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=83fde7eb-abab-e770-efd5-89bc9c39fdff@amd.com \
    --to=philip.yang-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@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.