From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: linux-sctp@vger.kernel.org,
lksctp-developers@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] sctp: do not enable peer features if we can't do them.
Date: Thu, 18 Sep 2008 23:01:29 -0400 [thread overview]
Message-ID: <48D31609.2090406@hp.com> (raw)
In-Reply-To: <20080918.162941.157950819.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Thu, 18 Sep 2008 17:31:03 -0400
>
>> Do not enable peer features like addip and auth, if they
>> are administratively disabled localy. If the peer resports
>> that he supports something that we don't, neither end can
>> use it so enabling it is pointless. This solves a problem
>> when talking to a peer that has auth and addip enabled while
>> we do not. Found by Andrei Pelinescu-Onciul <andrei@iptel.org>.
>>
>> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
>
> I applied this, but it is at best borderline for outside the
> merge window. It doesn't fix an OOPS nor a security issue nor
> an entry in the 2.6.x regression list, therefore strictly speaking
> this fix is not appropriate at this time.
>
> Please apply this criteria when deciding whether to submit future
> fixes for net-2.6 inclusion.
>
It is a major interoperability issue. With the default sysctl settings,
we can not establish connection to BSD systems. Yes, there is a workaround
of turning on the 2 required sysctl settings, but that is totally suboptimal.
I've thought about this fix for a while, and in my opinion, the interoperability
problem is large enough to warrant the fix at this time and the backport to
table.
Of course you are free to not include this in net-2.6, but I hope you will.
Thanks
-vlad
prev parent reply other threads:[~2008-09-19 3:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 21:31 [PATCH 1/2] sctp: do not enable peer features if we can't do them Vlad Yasevich
2008-09-18 21:31 ` [PATCH 2/2] sctp: Fix oops when INIT-ACK indicates that peer doesn't support AUTH Vlad Yasevich
2008-09-18 23:29 ` David Miller
2008-09-18 23:01 ` [Lksctp-developers] [PATCH 1/2] sctp: do not enable peer features if we can't do them Vlad Yasevich
2008-09-18 23:18 ` David Miller
2008-09-18 23:29 ` David Miller
2008-09-19 3:01 ` Vlad Yasevich [this message]
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=48D31609.2090406@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
/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).