[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADvbK_fAxF4s5_gmpwdRk9T92vjtnyNTykH8AJmRkbiZJNa6xQ@mail.gmail.com>
Date: Wed, 22 Dec 2021 10:54:23 -0500
From: Xin Long <lucien.xin@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Vlad Yasevich <vyasevich@...il.com>,
Neil Horman <nhorman@...driver.com>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
davem <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
"linux-sctp @ vger . kernel . org" <linux-sctp@...r.kernel.org>,
network dev <netdev@...r.kernel.org>
Subject: Re: SCTP ABI breakage?
On Tue, Dec 21, 2021 at 5:50 PM Stephen Hemminger
<stephen@...workplumber.org> wrote:
>
> Looks like changes to SCTP events create kernel ABI breakage in applications.
>
> If application is compiled with new header but attempts to run on older kernel, it doesn't work:
>
> Reported here: https://osmocom.org/issues/5366
>
> Looks like bad design assumptions about how setsockopt here:
> static int sctp_setsockopt_events(struct sock *sk, __u8 *sn_type,
> unsigned int optlen)
> {
> struct sctp_sock *sp = sctp_sk(sk);
> struct sctp_association *asoc;
> int i;
>
> if (optlen > sizeof(struct sctp_event_subscribe))
> return -EINVAL;
>
> Because of that the commits that add new events cause code built with the new
> header to not run on older kernels.
Hi, Stephen,
This is a known issue, and we're sorry that this can not be fixed.
please see:
https://lore.kernel.org/netdev/20200501131607.GU1294372@nataraja/
Thanks.
Powered by blists - more mailing lists