From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, agraf@suse.de, borntraeger@de.ibm.com,
jfrei@linux.vnet.ibm.com,
Cornelia Huck <cornelia.huck@de.ibm.com>,
"Eugene (jno) Dvurechenski" <jno@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PULL for-2.6 08/11] pc-bios/s390-ccw: fix old bug in ptr increment
Date: Fri, 11 Mar 2016 10:56:39 +0100 [thread overview]
Message-ID: <1457690202-10361-9-git-send-email-cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1457690202-10361-1-git-send-email-cornelia.huck@de.ibm.com>
From: "Eugene (jno) Dvurechenski" <jno@linux.vnet.ibm.com>
We need to increment by the size of the structure, whereas 'ns' is 'uint8_t *'.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Eugene (jno) Dvurechenski <jno@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
pc-bios/s390-ccw/bootmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pc-bios/s390-ccw/bootmap.c b/pc-bios/s390-ccw/bootmap.c
index 415508b..4925302 100644
--- a/pc-bios/s390-ccw/bootmap.c
+++ b/pc-bios/s390-ccw/bootmap.c
@@ -424,7 +424,7 @@ static void ipl_scsi(void)
IPL_assert(magic_match(sec, ZIPL_MAGIC), "No zIPL magic");
ns_end = sec + virtio_get_block_size();
- for (ns = (sec + pte_len); (ns + pte_len) < ns_end; ns++) {
+ for (ns = (sec + pte_len); (ns + pte_len) < ns_end; ns += pte_len) {
prog_table_entry = (ScsiBlockPtr *)ns;
if (!prog_table_entry->blockno) {
break;
--
2.7.2
next prev parent reply other threads:[~2016-03-11 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 9:56 [Qemu-devel] [PULL for-2.6 00/11] s390x patches for 2.6 Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 01/11] s390x/cpu: Cleanup init in preparation for hotplug Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 02/11] s390x/cpu: Set initial CPU state in common routine Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 03/11] s390x/cpu: Get rid of side effects when creating a vcpu Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 04/11] s390x/cpu: Tolerate max_cpus Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 05/11] s390x/cpu: Add CPU property links Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 06/11] s390x/cpu: Add error handling to cpu creation Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 07/11] s390x/cpu: Allow hotplug of CPUs Cornelia Huck
2016-03-11 9:56 ` Cornelia Huck [this message]
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 09/11] s390x: Introduce machine definition macros Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 10/11] s390x: Introduce S390MachineClass Cornelia Huck
2016-03-11 9:56 ` [Qemu-devel] [PULL for-2.6 11/11] s390x/cpu: use g_new0 Cornelia Huck
2016-03-14 11:49 ` [Qemu-devel] [PULL for-2.6 00/11] s390x patches for 2.6 Peter Maydell
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=1457690202-10361-9-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=jno@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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 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).