From: Daniel Borkmann <dborkman@redhat.com>
To: linux-sctp@vger.kernel.org
Subject: Re: uapi header mismatch with kernel ?
Date: Thu, 28 Aug 2014 13:12:31 +0000 [thread overview]
Message-ID: <53FF2ABF.30907@redhat.com> (raw)
In-Reply-To: <CA+sbV4gaHaEskjKiAZOGUXAr5zjbCF7F70KC01y9xgOb8KcPng@mail.gmail.com>
On 08/28/2014 03:05 PM, Tristan Su wrote:
> On Thu, Aug 28, 2014 at 3:47 PM, Daniel Borkmann <dborkman@redhat.com> wrote:
>> On 08/28/2014 09:34 AM, Daniel Borkmann wrote:
>>>
>>> On 08/28/2014 08:33 AM, 苏庆 wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I found that In 3.x kernel, the sctp states are defined differently
>>>> between kernel and uapi header. This makes our application fails to
>>>> work.
>>>>
>>>> Is that a mismatch or am I missing something?
>>>
>>>
>>> You are correct, and that's not good ... can you try out the below
>>> kernel patch?
>
> Thank you for the confirmation.
> I'm not kernel developer and have no experience on kernel patching/compiling
> but the fix looks straightforwards to me.
>
> It seems that the issue exists in mainline kernel and also distributions
> like RHEL7, Ubuntu 14.04, etc. Applications that care SCTP_STATUS
> would be impacted and it would not help even to recompile the application.
I'm currently verifying it myself and will send out a patch ASAP. It will
then go to stable afterwards on the next pull request from Dave to Linus.
> BTW, any idea on how long it would take for the fix to be delivered by
> distributions like RHEL?
>
> Should I report this to bugzilla.kernel.org or to linux distributions?
They will include it when it gets delivered via stable kernels.
prev parent reply other threads:[~2014-08-28 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 6:33 uapi header mismatch with kernel ? 苏庆
2014-08-28 7:34 ` Daniel Borkmann
2014-08-28 7:47 ` Daniel Borkmann
2014-08-28 13:05 ` Tristan Su
2014-08-28 13:12 ` Daniel Borkmann [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=53FF2ABF.30907@redhat.com \
--to=dborkman@redhat.com \
--cc=linux-sctp@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