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

    Remove printk from rds_sendmsg

to the 3.3-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:
     remove-printk-from-rds_sendmsg.patch
and it can be found in the queue-3.3 subdirectory.

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


>From c40b8d23db77c1023ac8bbb2bf6fcce6db76c7a5 Mon Sep 17 00:00:00 2001
From: Dave Jones <[email protected]>
Date: Mon, 19 Mar 2012 13:01:07 +0000
Subject: Remove printk from rds_sendmsg


From: Dave Jones <[email protected]>

[ Upstream commit a6506e1486181975d318344143aca722b2b91621 ]

no socket layer outputs a message for this error and neither should rds.

Signed-off-by: Dave Jones <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
 net/rds/send.c |    1 -
 1 file changed, 1 deletion(-)

--- a/net/rds/send.c
+++ b/net/rds/send.c
@@ -935,7 +935,6 @@ int rds_sendmsg(struct kiocb *iocb, stru
        /* Mirror Linux UDP mirror of BSD error message compatibility */
        /* XXX: Perhaps MSG_MORE someday */
        if (msg->msg_flags & ~(MSG_DONTWAIT | MSG_CMSG_COMPAT)) {
-               printk(KERN_INFO "msg_flags 0x%08X\n", msg->msg_flags);
                ret = -EOPNOTSUPP;
                goto out;
        }


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

queue-3.3/remove-printk-from-rds_sendmsg.patch
queue-3.3/usbnet-increase-urb-reference-count-before-usb_unlink_urb.patch
queue-3.3/mm-thp-fix-pmd_bad-triggering-in-code-paths-holding-mmap_sem-read-mode.patch
queue-3.3/net-fix-a-potential-rcu_read_lock-imbalance-in-rt6_fill_node.patch
queue-3.3/sysctl-protect-poll-in-entries-that-may-go-away.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