qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1785734] Re: movdqu partial write at page boundary


From: Thomas Huth
Subject: [Bug 1785734] Re: movdqu partial write at page boundary
Date: Tue, 11 May 2021 05:13:33 -0000

The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.

If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".

If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:

1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:

    https://gitlab.com/qemu-project/qemu/-/issues

and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.

2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).

Thank you and sorry for the inconvenience.


** Changed in: qemu
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1785734

Title:
  movdqu partial write at page boundary

Status in QEMU:
  Incomplete

Bug description:
  In TCG mode, when a 16-byte write instruction (such as movdqu) is
  executed at a page boundary and causes a page fault, a partial write
  is executed in the first page. See the attached code for an example.

  Tested on the qemu-3.0.0-rc1 release.

  % gcc -m32 qemu-bug2.c && ./a.out && echo && qemu-i386 ./a.out
  [snip]
  page fault: addr=0x70001000 err=0x7
  *(0x70000ff8+ 0) = aa
  *(0x70000ff8+ 1) = aa
  *(0x70000ff8+ 2) = aa
  *(0x70000ff8+ 3) = aa
  *(0x70000ff8+ 4) = aa
  *(0x70000ff8+ 5) = aa
  *(0x70000ff8+ 6) = aa
  *(0x70000ff8+ 7) = aa
  *(0x70000ff8+ 8) = 55
  *(0x70000ff8+ 9) = 55
  *(0x70000ff8+10) = 55
  *(0x70000ff8+11) = 55
  *(0x70000ff8+12) = 55
  *(0x70000ff8+13) = 55
  *(0x70000ff8+14) = 55
  *(0x70000ff8+15) = 55

  [snip]
  page fault: addr=0x70001000 err=0x6
  *(0x70000ff8+ 0) = 77
  *(0x70000ff8+ 1) = 66
  *(0x70000ff8+ 2) = 55
  *(0x70000ff8+ 3) = 44
  *(0x70000ff8+ 4) = 33
  *(0x70000ff8+ 5) = 22
  *(0x70000ff8+ 6) = 11
  *(0x70000ff8+ 7) = 0
  *(0x70000ff8+ 8) = 55
  *(0x70000ff8+ 9) = 55
  *(0x70000ff8+10) = 55
  *(0x70000ff8+11) = 55
  *(0x70000ff8+12) = 55
  *(0x70000ff8+13) = 55
  *(0x70000ff8+14) = 55
  *(0x70000ff8+15) = 55

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1785734/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]