From: Keith Seitz <keiths@redhat.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: insight@sourceware.org
Subject: Re: [PATCH 1/2] Add an assert that we're not overflowing the register cache.
Date: Thu, 05 Sep 2013 18:55:00 -0000 [thread overview]
Message-ID: <5228D3B2.6070507@redhat.com> (raw)
In-Reply-To: <5228947C.8040706@broadcom.com>
On 09/05/2013 07:26 AM, Andrew Burgess wrote:
> This patch doesn't fix the issue, but adds an assert to detect the bug.
If I understand correctly, the next patch fixes the actual problem, but
this is added in case it happens again. Yes?
> OK to apply?
Yes. Thanks!
Keith
next prev parent reply other threads:[~2013-09-05 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:24 [PATCH 0/2] Memory corruption caused by failure to notice architecture change Andrew Burgess
2013-09-05 14:26 ` [PATCH 1/2] Add an assert that we're not overflowing the register cache Andrew Burgess
2013-09-05 18:55 ` Keith Seitz [this message]
2013-09-06 9:36 ` Andrew Burgess
2013-09-05 14:27 ` [PATCH 2/2] Notice architecture changes even when the register window is not open Andrew Burgess
2013-09-05 19:53 ` Keith Seitz
2013-09-06 9:21 ` Andrew Burgess
2013-09-06 9:40 ` Andrew Burgess
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=5228D3B2.6070507@redhat.com \
--to=keiths@redhat.com \
--cc=aburgess@broadcom.com \
--cc=insight@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).