This is a note to let you know that I've just added the patch titled

    s390/kdump: fix REGSET_VX_LOW vector register ELF notes

to the 4.1-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     s390-kdump-fix-regset_vx_low-vector-register-elf-notes.patch
and it can be found in the queue-4.1 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 3c8e5105e759e7b2d88ea8a85b1285e535bc7500 Mon Sep 17 00:00:00 2001
From: Michael Holzheu <[email protected]>
Date: Thu, 11 Jun 2015 19:59:04 +0200
Subject: s390/kdump: fix REGSET_VX_LOW vector register ELF notes

From: Michael Holzheu <[email protected]>

commit 3c8e5105e759e7b2d88ea8a85b1285e535bc7500 upstream.

The REGSET_VX_LOW ELF notes should contain the lower 64 bit halfes of the
first sixteen 128 bit vector registers. Unfortunately currently we copy
the upper halfes.

Fix this and correctly copy the lower halfes.

Fixes: a62bc0739253 ("s390/kdump: add support for vector extension")
Signed-off-by: Michael Holzheu <[email protected]>
Signed-off-by: Martin Schwidefsky <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 arch/s390/kernel/crash_dump.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/arch/s390/kernel/crash_dump.c
+++ b/arch/s390/kernel/crash_dump.c
@@ -415,7 +415,7 @@ static void *nt_s390_vx_low(void *ptr, _
        ptr += len;
        /* Copy lower halves of SIMD registers 0-15 */
        for (i = 0; i < 16; i++) {
-               memcpy(ptr, &vx_regs[i], 8);
+               memcpy(ptr, &vx_regs[i].u[2], 8);
                ptr += 8;
        }
        return ptr;


Patches currently in stable-queue which might be from 
[email protected] are

queue-4.1/s390-kdump-fix-regset_vx_low-vector-register-elf-notes.patch
queue-4.1/s390-bpf-fix-backward-jumps.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to