SCTP: Reduce log spamming for sctp setsockopt
authorNeil Horman <nhorman@tuxdriver.com>
Mon, 23 Dec 2013 13:29:43 +0000 (08:29 -0500)
committerDavid S. Miller <davem@davemloft.net>
Tue, 31 Dec 2013 18:58:40 +0000 (13:58 -0500)
commit94f65193abbc07e4a4f3dbe3729ceb95c1493ea2
tree0d2ece1a60e17bdcf6a39bc58e8412ddc0cc7d6a
parent0a9a8bfd29aa5ba2298dc80852cdbb63a42f6576
SCTP: Reduce log spamming for sctp setsockopt

During a recent discussion regarding some sctp socket options, it was noted that
we have several points at which we issue log warnings that can be flooded at an
unbounded rate by any user.  Fix this by converting all the pr_warns in the
sctp_setsockopt path to be pr_warn_ratelimited.

Note there are several debug level messages as well.  I'm leaving those alone,
as, if you turn on pr_debug, you likely want lots of verbosity.

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
CC: Vlad Yasevich <vyasevich@gmail.com>
CC: David Miller <davem@davemloft.net>
CC: netdev@vger.kernel.org
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sctp/socket.c