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

    fix breakage in o2net_send_tcp_msg()

to the 3.17-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:
     fix-breakage-in-o2net_send_tcp_msg.patch
and it can be found in the queue-3.17 subdirectory.

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


>From 7e8631e8b9d4e9f698c09c7e7309c96249180ff9 Mon Sep 17 00:00:00 2001
From: Al Viro <[email protected]>
Date: Wed, 5 Nov 2014 15:18:29 -0500
Subject: fix breakage in o2net_send_tcp_msg()

From: Al Viro <[email protected]>

commit 7e8631e8b9d4e9f698c09c7e7309c96249180ff9 upstream.

uninitialized msghdr.  Broken in "ocfs2: don't open-code kernel_recvmsg()"
by me ;-/

Signed-off-by: Al Viro <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/ocfs2/cluster/tcp.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/ocfs2/cluster/tcp.c
+++ b/fs/ocfs2/cluster/tcp.c
@@ -925,7 +925,7 @@ static int o2net_send_tcp_msg(struct soc
                              size_t veclen, size_t total)
 {
        int ret;
-       struct msghdr msg;
+       struct msghdr msg = {.msg_flags = 0,};
 
        if (sock == NULL) {
                ret = -EINVAL;


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

queue-3.17/fs-fix-theoretical-division-by-0-in-super_cache_scan.patch
queue-3.17/fs-make-cont_expand_zero-interruptible.patch
queue-3.17/fix-inode-leaks-on-d_splice_alias-failure-exits.patch
queue-3.17/fix-misuses-of-f_count-in-ppp-and-netlink.patch
queue-3.17/missing-data-dependency-barrier-in-prepend_name.patch
queue-3.17/kill-wbuf_queued-wbuf_dwork_lock.patch
queue-3.17/fix-breakage-in-o2net_send_tcp_msg.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