From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] sctp/sctp_big_chunk.c: Add a hint on failure with EINVAL
Date: Thu, 12 Apr 2018 14:39:10 +0800 [thread overview]
Message-ID: <5ACEFF0E.2030505@cn.fujitsu.com> (raw)
In-Reply-To: <b53044f2-18fc-393e-48fd-dd5700ddfc8b@oracle.com>
On 2018/04/11 22:30, Alexey Kodanev wrote:
> On 05.04.2018 13:27, Xiao Yang wrote:
>> If two ipv6 addresses have same family, a buggy kernel(e.g. RHEL6) lacked
>> the port check for them, and made this test get a failure with EINVAL:
>> -------------------------------------------------------------------------
>> safe_net.c:160: BROK: sctp_big_chunk.c:77: setsockopt(4, 132, 100, 0x7ffdbaac83a0, 91644) failed: EINVAL
>> -------------------------------------------------------------------------
>>
>> If you want to know detailed info for the bug, please see the following commit:
>> '40b4f0f (sctp: lack the check for ports in sctp_v6_cmp_addr)'
>>
>> We just want to hint users about the likely cause of the failure.
> I guess, the test will fail with EINVAL with this patch,
>
> https://patchwork.ozlabs.org/patch/897172/
>
> it tries to avoid the check with ports so it won't be possible
> to pass the same addresses like the test does, it is currently
> in ML.
Hi Alexey,
Thanks for your explanation.
Before commit 40b4f0f, it also failed with EINVAL because of the same ipv6 addresses.
Do you want to apply the first version of the test?
Thanks,
Xiao Yang
> The first version of the test would work but it can be slower
> for some VMs, because it creates unique addresses.
>
> http://lists.linux.it/pipermail/ltp/2018-March/007269.html
>
> Thanks,
> Alexey
>
>
>
next prev parent reply other threads:[~2018-04-12 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 10:27 [LTP] [PATCH] sctp/sctp_big_chunk.c: Add a hint on failure with EINVAL Xiao Yang
2018-04-11 14:30 ` Alexey Kodanev
2018-04-12 6:39 ` Xiao Yang [this message]
2018-04-12 11:15 ` Alexey Kodanev
2018-04-21 6:06 ` Xiao Yang
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=5ACEFF0E.2030505@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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