From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42980] BUG in gfn_to_pfn_prot
Date: Wed, 15 Aug 2012 22:24:36 +0000 (UTC) [thread overview]
Message-ID: <20120815222436.DD68C11FA5F@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42980-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42980
Luke-Jr <luke-jr+linuxbugs@utopios.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|CODE_FIX |
--- Comment #12 from Luke-Jr <luke-jr+linuxbugs@utopios.org> 2012-08-15 22:24:36 ---
Sorry I didn't report it sooner, but I have had the same crash since June, with
this patch. :(
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-08-15 22:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 21:28 [Bug 42980] New: BUG in gfn_to_pfn_prot bugzilla-daemon
2012-03-28 13:03 ` [Bug 42980] " bugzilla-daemon
2012-03-28 13:37 ` bugzilla-daemon
2012-03-28 13:45 ` bugzilla-daemon
2012-03-28 13:49 ` bugzilla-daemon
2012-03-28 15:07 ` bugzilla-daemon
2012-05-10 10:53 ` bugzilla-daemon
2012-05-10 13:17 ` bugzilla-daemon
2012-05-10 13:30 ` bugzilla-daemon
2012-05-17 20:58 ` bugzilla-daemon
2012-06-16 3:16 ` bugzilla-daemon
2012-07-01 9:46 ` bugzilla-daemon
2012-08-15 21:58 ` bugzilla-daemon
2012-08-15 22:24 ` bugzilla-daemon [this message]
2012-08-15 22:34 ` bugzilla-daemon
2012-08-15 22:38 ` bugzilla-daemon
2012-08-15 22:47 ` bugzilla-daemon
2012-08-16 9:32 ` bugzilla-daemon
2012-11-17 22:00 ` bugzilla-daemon
2012-11-17 22:10 ` bugzilla-daemon
2012-11-18 14:15 ` Avi Kivity
2012-11-18 14:15 ` bugzilla-daemon
2012-11-18 17:06 ` bugzilla-daemon
2012-12-08 20:50 ` bugzilla-daemon
2014-06-25 2:11 ` 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=20120815222436.DD68C11FA5F@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 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).