From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: vyasevic@redhat.com, nhorman@tuxdriver.com,
David.Laight@ACULAB.COM, netdev@vger.kernel.org,
Michael Tuexen <tuexen@fh-muenster.de>
Subject: Re: [PATCH net] net: sctp: stop spamming klog with rfc6458, 5.3.2. deprecation warnings
Date: Wed, 22 Jul 2015 10:43:40 -0400 [thread overview]
Message-ID: <55AFAC1C.7090000@mojatatu.com> (raw)
In-Reply-To: <04fbd47379461dc2cb145117a9f81ecc68de7221.1437575142.git.daniel@iogearbox.net>
On 07/22/15 10:31, Daniel Borkmann wrote:
> Back then when we added support for SCTP_SNDINFO/SCTP_RCVINFO from
> RFC6458 5.3.4/5.3.5, we decided to add a deprecation warning for the
> (as per RFC deprecated) SCTP_SNDRCV via commit bbbea41d5e53 ("net:
> sctp: deprecate rfc6458, 5.3.2. SCTP_SNDRCV support"), see [1].
>
> Imho, it was not a good idea, and we should just revert that message
> for a couple of reasons:
>
> 1) It's uapi and therefore set in stone forever.
>
> 2) To be able to run on older and newer kernels, an SCTP application
> would need to probe for both, SCTP_SNDRCV, but also SCTP_SNDINFO/
> SCTP_RCVINFO support, so that on older kernels, it can make use
> of SCTP_SNDRCV, and on newer kernels SCTP_SNDINFO/SCTP_RCVINFO.
> In my (limited) experience, a lot of SCTP appliances are migrating
> to newer kernels only ve(ee)ry slowly.
>
> 3) Some people don't have the chance to change their applications,
> f.e. due to proprietary legacy stuff. So, they'll hit this warning
> in fast path and are stuck with older kernels.
>
> But i.e. due to point 1) I really fail to see the benefit of a warning.
> So just revert that for now, the issue was reported up Jamal.
>
> [1] http://thread.gmane.org/gmane.linux.network/321960/
>
> Reported-by: Jamal Hadi Salim <jhs@mojatatu.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Michael Tuexen <tuexen@fh-muenster.de>
Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
cheers,
jamal
next prev parent reply other threads:[~2015-07-22 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:31 [PATCH net] net: sctp: stop spamming klog with rfc6458, 5.3.2. deprecation warnings Daniel Borkmann
2015-07-22 14:43 ` Jamal Hadi Salim [this message]
2015-07-22 14:46 ` Michael Tuexen
2015-07-26 23:32 ` David Miller
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=55AFAC1C.7090000@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=David.Laight@ACULAB.COM \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tuexen@fh-muenster.de \
--cc=vyasevic@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.