From: Launchpad Bug Tracker <1783437@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1783437] Re: read-modify-write page faults error code has write bit unset
Date: Fri, 02 Jul 2021 04:17:16 -0000 [thread overview]
Message-ID: <162519943698.31921.5133309425493873694.malone@loganberry.canonical.com> (raw)
In-Reply-To: 153247670930.31632.15065752803528835886.malonedeb@chaenomeles.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1783437
Title:
read-modify-write page faults error code has write bit unset
Status in QEMU:
Expired
Bug description:
Consider the attached C file, which does a read-modify-write of the
form `add [mem], reg`, where `mem` points to a non-present page. In
the resulting page fault, the W/R bit is not set, while real hardware
does set this bit.
% gcc -m32 qemu-bug1.c&& ./a.out && qemu-i386 ./a.out
page fault: addr=0x70000000 err=0x6
page fault: addr=0x70000000 err=0x4
Tested on the qemu-3.0.0-rc1 release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1783437/+subscriptions
prev parent reply other threads:[~2021-07-02 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 23:58 [Qemu-devel] [Bug 1783437] [NEW] read-modify-write page faults error code has write bit unset Fabian Hemmer
2021-05-02 5:47 ` [Bug 1783437] " Thomas Huth
2021-07-02 4:17 ` Launchpad Bug Tracker [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=162519943698.31921.5133309425493873694.malone@loganberry.canonical.com \
--to=1783437@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.