From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
lksctp-developers@lists.sourceforge.net
Subject: Re: [Lksctp-developers] [PATCH 1/2] sctp: do not enable peer features
Date: Thu, 18 Sep 2008 23:01:23 +0000 [thread overview]
Message-ID: <48D2DDC3.3060406@hp.com> (raw)
In-Reply-To: <1221773464-28845-1-git-send-email-vladislav.yasevich@hp.com>
David
Can you also queue this one and Patch 2/2 to stable. The problems
are there as well.
Thanks
-vlad
Vlad Yasevich wrote:
> 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>
> ---
> net/sctp/sm_make_chunk.c | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/net/sctp/sm_make_chunk.c b/net/sctp/sm_make_chunk.c
> index e8ca4e5..fe94f42 100644
> --- a/net/sctp/sm_make_chunk.c
> +++ b/net/sctp/sm_make_chunk.c
> @@ -1886,11 +1886,13 @@ static void sctp_process_ext_param(struct sctp_association *asoc,
> /* if the peer reports AUTH, assume that he
> * supports AUTH.
> */
> - asoc->peer.auth_capable = 1;
> + if (sctp_auth_enable)
> + asoc->peer.auth_capable = 1;
> break;
> case SCTP_CID_ASCONF:
> case SCTP_CID_ASCONF_ACK:
> - asoc->peer.asconf_capable = 1;
> + if (sctp_addip_enable)
> + asoc->peer.asconf_capable = 1;
> break;
> default:
> break;
> @@ -2460,6 +2462,9 @@ do_addr_param:
> break;
>
> case SCTP_PARAM_SET_PRIMARY:
> + if (!sctp_addip_enable)
> + goto fall_through;
> +
> addr_param = param.v + sizeof(sctp_addip_param_t);
>
> af = sctp_get_af_specific(param_type2af(param.p->type));
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
lksctp-developers@lists.sourceforge.net
Subject: Re: [Lksctp-developers] [PATCH 1/2] sctp: do not enable peer features if we can't do them.
Date: Thu, 18 Sep 2008 19:01:23 -0400 [thread overview]
Message-ID: <48D2DDC3.3060406@hp.com> (raw)
In-Reply-To: <1221773464-28845-1-git-send-email-vladislav.yasevich@hp.com>
David
Can you also queue this one and Patch 2/2 to stable. The problems
are there as well.
Thanks
-vlad
Vlad Yasevich wrote:
> 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>
> ---
> net/sctp/sm_make_chunk.c | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/net/sctp/sm_make_chunk.c b/net/sctp/sm_make_chunk.c
> index e8ca4e5..fe94f42 100644
> --- a/net/sctp/sm_make_chunk.c
> +++ b/net/sctp/sm_make_chunk.c
> @@ -1886,11 +1886,13 @@ static void sctp_process_ext_param(struct sctp_association *asoc,
> /* if the peer reports AUTH, assume that he
> * supports AUTH.
> */
> - asoc->peer.auth_capable = 1;
> + if (sctp_auth_enable)
> + asoc->peer.auth_capable = 1;
> break;
> case SCTP_CID_ASCONF:
> case SCTP_CID_ASCONF_ACK:
> - asoc->peer.asconf_capable = 1;
> + if (sctp_addip_enable)
> + asoc->peer.asconf_capable = 1;
> break;
> default:
> break;
> @@ -2460,6 +2462,9 @@ do_addr_param:
> break;
>
> case SCTP_PARAM_SET_PRIMARY:
> + if (!sctp_addip_enable)
> + goto fall_through;
> +
> addr_param = param.v + sizeof(sctp_addip_param_t);
>
> af = sctp_get_af_specific(param_type2af(param.p->type));
next prev parent reply other threads:[~2008-09-18 23:01 UTC|newest]
Thread overview: 14+ 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 ` 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 21:31 ` Vlad Yasevich
2008-09-18 23:29 ` [PATCH 2/2] sctp: Fix oops when INIT-ACK indicates that peer David Miller
2008-09-18 23:29 ` [PATCH 2/2] sctp: Fix oops when INIT-ACK indicates that peer doesn't support AUTH David Miller
2008-09-18 23:01 ` Vlad Yasevich [this message]
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 ` [Lksctp-developers] [PATCH 1/2] sctp: do not enable peer David Miller
2008-09-18 23:18 ` [Lksctp-developers] [PATCH 1/2] sctp: do not enable peer features if we can't do them David Miller
2008-09-18 23:29 ` [PATCH 1/2] sctp: do not enable peer features if we can't do David Miller
2008-09-18 23:29 ` [PATCH 1/2] sctp: do not enable peer features if we can't do them David Miller
2008-09-19 3:01 ` [PATCH 1/2] sctp: do not enable peer features if we can't do Vlad Yasevich
2008-09-19 3:01 ` [PATCH 1/2] sctp: do not enable peer features if we can't do them 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=48D2DDC3.3060406@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 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.