kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: brijesh.singh@amd.com, kvm@vger.kernel.org
Subject: Re: [bug report] KVM: SVM: Add KVM_SEND_UPDATE_DATA command
Date: Thu, 6 May 2021 18:09:54 +0000	[thread overview]
Message-ID: <YJQw8jlJcPO9ImNO@google.com> (raw)
In-Reply-To: <YIpeKpSB7Wqkqn9f@mwanda>

On Thu, Apr 29, 2021, Dan Carpenter wrote:
> Hello Brijesh Singh,
> The patch d3d1af85e2c7: "KVM: SVM: Add KVM_SEND_UPDATE_DATA command"
> from Apr 15, 2021, leads to the following static checker warning:
> arch/x86/kvm/svm/sev.c:1268 sev_send_update_data() warn: 'guest_page' is an error pointer or valid
> arch/x86/kvm/svm/sev.c:1316 sev_send_update_data() warn: maybe return -EFAULT instead of the bytes remaining?
> arch/x86/kvm/svm/sev.c:1462 sev_receive_update_data() warn: 'guest_page' is an error pointer or valid

Thanks for the report.  Is the static checker you're using publicly available?
Catching these bugs via a checker is super cool!

  reply	other threads:[~2021-05-06 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  7:20 [bug report] KVM: SVM: Add KVM_SEND_UPDATE_DATA command Dan Carpenter
2021-05-06 18:09 ` Sean Christopherson [this message]
2021-05-07  5:01   ` Dan Carpenter

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YJQw8jlJcPO9ImNO@google.com \
    --to=seanjc@google.com \
    --cc=brijesh.singh@amd.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kvm@vger.kernel.org \


* 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).