On Tue, Oct 8, 2019 at 9:02 PM David Laight <david.lai...@aculab.com> wrote: > > From: Xin Long > > Sent: 08 October 2019 12:25 > > > > This is a sockopt defined in section 7.3 of rfc7829: "Exposing > > the Potentially Failed Path State", by which users can change > > pf_expose per sock and asoc. > > If I read these patches correctly the default for this sockopt in 'enabled'. > Doesn't this mean that old application binaries will receive notifications > that they aren't expecting? > > I'd have thought that applications would be required to enable it. If we do that, sctp_getsockopt_peer_addr_info() in patch 2/5 breaks.
> > David > > - > Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 > 1PT, UK > Registration No: 1397386 (Wales) >
