From: Neil Horman <nhorman@tuxdriver.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Vlad Yasevich <vyasevich@gmail.com>,
Daniel Borkmann <dborkman@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"geirola@gmail.com" <geirola@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH net-next 0/5] SCTP updates
Date: Thu, 10 Jul 2014 10:55:52 +0000 [thread overview]
Message-ID: <20140710105552.GA4437@hmsreliant.think-freely.org> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1726FBA0@AcuExch.aculab.com>
On Thu, Jul 10, 2014 at 09:02:23AM +0000, David Laight wrote:
> From: Neil Horman
> ...
> > > No there is not direct overlap between the two. However, as Michael pointed out,
> > > there is a new option to control SCTP_RCVINFO. So would could add a deprecation
> > > warning to the over SCTP_EVENTS option and carry SCTP_SNDRCVINFO with it.
> > > Once SCTP_EVENTS goes away so can SCTP_SNDRCVINFO.
> > >
> > Ok, so we should still consider deprecation warnings then. Daniel, what about
> > ratelimited warnings with pids included then?
>
> Can you defer any deprecation warnings for a few kernel versions?
> This gives time for applications to be recoded.
I'm not sure I understand the reasoning here? Why should a deprecation warning
be delayed so you can recode your application? What about all the people who
aren't subscribed this list? That just furhter delays their finding out about
the deprecation.
> Including argv[0] (even just the exec-time value) is much more use than the pid.
>
Thats fine, I think deprecation warnings usually have the form "[deprecated] pid
%d(%s)..." where %s is argv[0].
> Actually this is 'right PITA' for an application.
> A program binary that needs to work with old and new kernels will have to
> try the new option, and if it fails fall back to the old one, and then
> conditionally create/inspect the cmsg data.
> I can't actually imagine anyone bothering!
>
A deprecation warning is just that, a warning, it doesn't cause the old
method to fail, its just a heads up to the application developer that they need
to make a change sometime in the next 5 years. If you implement the new method
in your application, you can wait for a reasonable period of time until you are
confident that you application isn't being used on older kernels, or bump the
minimal kernel version to run your app, and cut over to the new method.
> Our sctp code is actually in a kernel module, so we can look at the kernel
> version when (part of) the driver is compiled on the target system.
>
You can do that too if you would like.
Neil
> David
>
>
>
>
next prev parent reply other threads:[~2014-07-10 10:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 21:05 [PATCH net-next 0/5] SCTP updates Daniel Borkmann
2014-07-04 21:05 ` [PATCH net-next 1/5] net: sctp: fix information leaks in ulpevent layer Daniel Borkmann
2014-07-04 21:05 ` [PATCH net-next 5/5] net: sctp: implement rfc6458, 8.1.31. SCTP_DEFAULT_SNDINFO support Daniel Borkmann
2014-07-08 11:14 ` [PATCH net-next 0/5] SCTP updates Neil Horman
2014-07-08 14:05 ` Daniel Borkmann
2014-07-08 14:41 ` Neil Horman
2014-07-09 9:57 ` Daniel Borkmann
2014-07-09 10:49 ` Neil Horman
2014-07-09 11:12 ` David Laight
2014-07-09 13:28 ` Daniel Borkmann
2014-07-09 15:13 ` Neil Horman
2014-07-09 15:25 ` Daniel Borkmann
2014-07-09 15:41 ` Neil Horman
2014-07-09 15:36 ` Vlad Yasevich
2014-07-09 15:44 ` Neil Horman
2014-07-09 16:02 ` David Laight
2014-07-09 16:12 ` Michael Tuexen
2014-07-09 16:30 ` Vlad Yasevich
2014-07-09 16:32 ` Vlad Yasevich
2014-07-09 18:35 ` Neil Horman
2014-07-10 9:02 ` David Laight
2014-07-10 9:37 ` Daniel Borkmann
2014-07-10 10:57 ` Neil Horman
2014-07-10 19:04 ` Vlad Yasevich
2014-07-10 10:55 ` Neil Horman [this message]
2014-07-09 16:10 ` Daniel Borkmann
2014-07-08 21:40 ` David Miller
2014-07-09 7:59 ` Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2008-12-20 1:47 [PATCH net-next 0/5]: " Vlad Yasevich
2008-12-20 1:47 ` Vlad Yasevich
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=20140710105552.GA4437@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=geirola@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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