From: Joe Perches <joe@perches.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] SCTP: Reduce log spamming for sctp setsockopt
Date: Mon, 16 Dec 2013 07:03:53 -0800 [thread overview]
Message-ID: <1387206233.18217.21.camel@joe-AO722> (raw)
In-Reply-To: <1387205049-22752-1-git-send-email-nhorman@tuxdriver.com>
On Mon, 2013-12-16 at 09:44 -0500, Neil Horman wrote:
> 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.
trivial note:
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
[]
> @@ -2579,8 +2579,8 @@ static int sctp_setsockopt_delayed_ack(struct sock *sk,
[]
> + pr_warn_ratelimited("Use of struct sctp_assoc_value in delayed_ack socket option deprecated\n");
> + pr_warn_ratelimited("Use struct sctp_sack_info instead\n");
[]
> @@ -2995,8 +2995,8 @@ static int sctp_setsockopt_maxseg(struct sock *sk, char __user *optval, unsigned
> + pr_warn_ratelimited("Use of int in maxseg socket option deprecated\n");
[]
> @@ -3253,8 +3253,8 @@ static int sctp_setsockopt_maxburst(struct sock *sk,
[]
> + pr_warn_ratelimited("Use of int in max_burst socket option deprecated\n");
> + pr_warn_ratelimited("Use struct sctp_assoc_value instead\n");
[]
> @@ -4574,8 +4574,8 @@ static int sctp_getsockopt_delayed_ack(struct sock *sk, int len,
[]
> + pr_warn_ratelimited("Use of struct sctp_assoc_value in delayed_ack socket option deprecated\n");
> + pr_warn_ratelimited("Use struct sctp_sack_info instead\n");
[]
> @@ -5219,8 +5219,8 @@ static int sctp_getsockopt_maxseg(struct sock *sk, int len,
[]
> + pr_warn_ratelimited("Use of int in maxseg socket option deprecated\n");
> + pr_warn_ratelimited("Use struct sctp_assoc_value instead\n");
[]
> @@ -5311,8 +5311,8 @@ static int sctp_getsockopt_maxburst(struct sock *sk, int len,
[]
> + pr_warn_ratelimited("Use of int in max_burst socket option deprecated\n");
> + pr_warn_ratelimited("Use struct sctp_assoc_value instead\n");
Perhaps a dedicated "deprecated" warning function
to centralize these?
void _sctp_warn_deprecated(const char *func, const char *from, const char *to);
{
etc.
}
#define sctp_warn_deprecated(from, to) \
_sctp_warn_deprecated(__func__, from, to)
and use
sctp_warn_deprecated("struct sctp_assoc_value", "struct sctp_sack_info");
sctp_warn_deprecated("int", "");
sctp_warn_deprecated("int", "struct sctp_assoc_value");
sctp_warn_deprecated("struct sctp_assoc_value", "struct sctp_sack_info");
sctp_warn_deprecated("int", "struct sctp_assoc_value");
sctp_warn_deprecated("int", "struct sctp_assoc_value");
next prev parent reply other threads:[~2013-12-16 15:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 14:44 [PATCH] SCTP: Reduce log spamming for sctp setsockopt Neil Horman
2013-12-16 15:03 ` Joe Perches [this message]
2013-12-16 15:13 ` Daniel Borkmann
2013-12-16 15:21 ` Joe Perches
2013-12-16 15:45 ` Daniel Borkmann
2013-12-16 16:04 ` Neil Horman
2013-12-16 16:50 ` Joe Perches
2013-12-16 17:02 ` Neil Horman
2013-12-16 17:17 ` Joe Perches
2013-12-16 17:04 ` Daniel Borkmann
2013-12-16 15:24 ` David Laight
2013-12-16 15:44 ` Neil Horman
2013-12-16 17:06 ` [PATCH v2 0/2] sctp: Consolidate and ratelimit deprecation warnings Neil Horman
2013-12-16 17:06 ` [PATCH v2 2/2] SCTP: Reduce log spamming for sctp setsockopt Neil Horman
2013-12-17 16:19 ` [PATCH v3 0/2] sctp: Consolidate and ratelimit deprecation warnings Neil Horman
2013-12-17 16:19 ` [PATCH v3 2/2] SCTP: Reduce log spamming for sctp setsockopt Neil Horman
2013-12-22 22:56 ` [PATCH v3 0/2] sctp: Consolidate and ratelimit deprecation warnings David Miller
2013-12-23 13:19 ` Neil Horman
2013-12-23 13:29 ` [PATCH v4 " Neil Horman
2013-12-23 13:29 ` [PATCH v4 1/2] printk: Add a DEPRECATED macro Neil Horman
2013-12-23 13:29 ` [PATCH v4 2/2] SCTP: Reduce log spamming for sctp setsockopt Neil Horman
2013-12-23 22:55 ` [PATCH v4 0/2] sctp: Consolidate and ratelimit deprecation warnings Ben Hutchings
2013-12-24 13:37 ` Neil Horman
2013-12-31 19:00 ` David Miller
2013-12-31 20:08 ` Joe Perches
2014-01-02 14:31 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1387206233.18217.21.camel@joe-AO722 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).