From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: "Christian König" <christian.koenig@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: kvm-vm boot fail: ttm_bo_cleanup_memtype_use?
Date: Tue, 6 Jul 2021 10:34:46 +0200 [thread overview]
Message-ID: <ab86c676-2753-6670-87de-57e1043c61c3@kernel.org> (raw)
In-Reply-To: <fef73358-748f-f1d0-bca9-43efa6497f44@amd.com>
On 7/6/21 8:53 AM, Christian König wrote:
> Hi Daniel,
>
> looks like a simple missing NULL check to me. Please test the attached patch.
>
It works!
Feel free to add:
Reported-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Tested-by: Daniel Bristot de Oliveira <bristot@kernel.org>
> We recently changed the structure of the resources, so probably introduced while
> doing that.
>
> Christian.
Thanks!
-- Daniel
prev parent reply other threads:[~2021-07-06 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:57 kvm-vm boot fail: ttm_bo_cleanup_memtype_use? Daniel Bristot de Oliveira
2021-07-06 6:53 ` Christian König
2021-07-06 8:34 ` Daniel Bristot de Oliveira [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=ab86c676-2753-6670-87de-57e1043c61c3@kernel.org \
--to=bristot@kernel.org \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).