All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 214165] New: Missing clflush before RECEIVE_UPDATE_DATA
Date: Tue, 24 Aug 2021 11:52:46 +0000	[thread overview]
Message-ID: <bug-214165-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=214165

            Bug ID: 214165
           Summary: Missing clflush before RECEIVE_UPDATE_DATA
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.13.12
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: masa.koz@seera-networks.com
        Regression: No

Created attachment 298457
  --> https://bugzilla.kernel.org/attachment.cgi?id=298457&action=edit
Add the missing sev_clflush_pages()

In sev_receive_update_data(), sev_clflush_pages() is not called b/w
sev_pin_memory() and RECEIVE_UPDATE_DATA. Because of this missing, we will
often see the pre-written contents in the memory updated by
RECEIVE_UPDATE_DATA. I guess that we should call sev_clflush_pages() as
LAUNCH_UPDATE_DATA.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-08-24 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 11:52 bugzilla-daemon [this message]
2021-09-13 23:06 ` [Bug 214165] Missing clflush before RECEIVE_UPDATE_DATA bugzilla-daemon

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=bug-214165-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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.