From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] scpt: Allow struct sctp_event_subscribe to grow without breaking binaries
Date: Wed, 04 Apr 2012 18:05:52 -0400 (EDT) [thread overview]
Message-ID: <20120404.180552.936202389292040147.davem@davemloft.net> (raw)
In-Reply-To: <4F7C5204.9040703@hp.com>
From: Vladislav Yasevich <vladislav.yasevich@hp.com>
Date: Wed, 04 Apr 2012 09:52:04 -0400
> On 04/04/2012 04:17 AM, Thomas Graf wrote:
>> getsockopt(..., SCTP_EVENTS, ...) performs a length check and returns
>> an error if the user provides less bytes than the size of struct
>> sctp_event_subscribe.
>>
>> Struct sctp_event_subscribe needs to be extended by an u8 for every
>> new event or notification type that is added.
>>
>> This obviously makes getsockopt fail for binaries that are compiled
>> against an older versions of <net/sctp/user.h> which do not contain
>> all event types.
>>
>> This patch changes getsockopt behaviour to no longer return an error
>> if not enough bytes are being provided by the user. Instead, it
>> returns as much of sctp_event_subscribe as fits into the provided buffer.
>>
>> This leads to the new behavior that users see what they have been aware
>> of at compile time.
>>
>> The setsockopt(..., SCTP_EVENTS, ...) API is already behaving like this.
>>
>> Signed-off-by: Thomas Graf <tgraf@suug.ch>
>
> Acked-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Applied, but I had to fix the Subject to read "sctp: " not "scpt: " :-)
next prev parent reply other threads:[~2012-04-04 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 8:17 [PATCH] scpt: Allow struct sctp_event_subscribe to grow without breaking binaries Thomas Graf
2012-04-04 13:52 ` Vladislav Yasevich
2012-04-04 22:05 ` David Miller [this message]
2012-04-04 22:13 ` Thomas Graf
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=20120404.180552.936202389292040147.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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;
as well as URLs for NNTP newsgroup(s).