linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yang, Philip" <Philip.Yang@amd.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Michel Dänzer" <michel@daenzer.net>,
	"Jérôme Glisse" <jglisse@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: KASAN caught amdgpu / HMM use-after-free
Date: Wed, 27 Feb 2019 18:48:30 +0000	[thread overview]
Message-ID: <b81bd33a-0041-392e-2c85-19036fc1c91d@amd.com> (raw)
In-Reply-To: <BN6PR12MB18090BDFE1DD800785C5ED76F7740@BN6PR12MB1809.namprd12.prod.outlook.com>

Hi Alex,

Pushed, thanks.

mm/hmm: use reference counting for HMM struct

Philip

On 2019-02-27 1:32 p.m., Deucher, Alexander wrote:
> Go ahead an apply it to amd-staging-drm-next.  It'll naturally fall out 
> when I rebase it.
> 
> Alex
> ------------------------------------------------------------------------
> *From:* amd-gfx <amd-gfx-bounces@lists.freedesktop.org> on behalf of 
> Yang, Philip <Philip.Yang@amd.com>
> *Sent:* Wednesday, February 27, 2019 1:05 PM
> *To:* Michel Dänzer; Jérôme Glisse
> *Cc:* linux-mm@kvack.org; amd-gfx@lists.freedesktop.org
> *Subject:* Re: KASAN caught amdgpu / HMM use-after-free
> amd-staging-drm-next will rebase to kernel 5.1 to pickup this fix
> automatically. As a short-term workaround, please cherry-pick this fix
> into your local repository.
> 
> Regards,
> Philip
> 
> On 2019-02-27 12:33 p.m., Michel Dänzer wrote:
>> On 2019-02-27 6:14 p.m., Yang, Philip wrote:
>>> 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.
>> 
>> Please push it to amd-staging-drm-next, so that others don't run into
>> the issue as well.
>> 
>> 
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2019-02-27 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 17:02 Michel Dänzer
2019-02-27 17:14 ` Yang, Philip
2019-02-27 17:33   ` Michel Dänzer
2019-02-27 18:05     ` Yang, Philip
2019-02-27 18:32       ` Deucher, Alexander
2019-02-27 18:48         ` Yang, Philip [this message]
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=b81bd33a-0041-392e-2c85-19036fc1c91d@amd.com \
    --to=philip.yang@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=michel@daenzer.net \
    /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