This is a note to let you know that I've just added the patch titled
tools: ffs-test: fix header values endianess
to the 3.15-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:
tools-ffs-test-fix-header-values-endianess.patch
and it can be found in the queue-3.15 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From f35f71244da6e51db4e1f2c7e318581f498ececf Mon Sep 17 00:00:00 2001
From: Michal Nazarewicz <mina86@xxxxxxxxxx>
Date: Fri, 13 Jun 2014 15:38:05 +0200
Subject: tools: ffs-test: fix header values endianess
From: Michal Nazarewicz <mina86@xxxxxxxxxx>
commit f35f71244da6e51db4e1f2c7e318581f498ececf upstream.
It appears that no one ever run ffs-test on a big-endian machine,
since it used cpu-endianess for fs_count and hs_count fields which
should be in little-endian format. Fix by wrapping the numbers in
cpu_to_le32.
Signed-off-by: Michal Nazarewicz <mina86@xxxxxxxxxx>
Signed-off-by: Felipe Balbi <balbi@xxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
tools/usb/ffs-test.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/tools/usb/ffs-test.c
+++ b/tools/usb/ffs-test.c
@@ -116,8 +116,8 @@ static const struct {
.header = {
.magic = cpu_to_le32(FUNCTIONFS_DESCRIPTORS_MAGIC),
.length = cpu_to_le32(sizeof descriptors),
- .fs_count = 3,
- .hs_count = 3,
+ .fs_count = cpu_to_le32(3),
+ .hs_count = cpu_to_le32(3),
},
.fs_descs = {
.intf = {
Patches currently in stable-queue which might be from mina86@xxxxxxxxxx are
queue-3.15/tools-ffs-test-fix-header-values-endianess.patch
queue-3.15/usb-gadget-f_fs-fix-null-pointer-dereference-when-there-are-no-strings.patch
queue-3.15/usb-gadget-f_fs-resurect-usb_functionfs_descs_head-structure.patch
queue-3.15/mm-page_alloc-fix-cma-area-initialisation-when-pageblock-max_order.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html