From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp] syscalls/bind03: Add version compare according to behaviour difference.
Date: Fri, 31 Aug 2018 10:41:50 +0200 [thread overview]
Message-ID: <20180831084149.GA16417@rei.lan> (raw)
In-Reply-To: <20180831132453.6461-1-junchi.chen@intel.com>
Hi!
> ISSUE:
> The case is designed to test the behaviour diverse caused by kernel
> commit 0fb44559ffd6. And it failed for the new behaviour.
>
> ACTION:
> Add a version compare to split part of the test.
This is actually a not-yet fixed kernel bug as the correct errno to be
reported in this case is EADDRINUSE at least that is what I understand
after reading POSIX.
See:
https://patchwork.ozlabs.org/patch/782692/
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-08-31 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 13:24 [LTP] [PATCH ltp] syscalls/bind03: Add version compare according to behaviour difference Junchi Chen
2018-08-31 8:37 ` Petr Vorel
2018-08-31 8:42 ` Cyril Hrubis
2018-09-07 10:12 ` Petr Vorel
2018-08-31 8:48 ` Xiao Yang
2018-08-31 9:34 ` Cyril Hrubis
2018-08-31 8:41 ` Cyril Hrubis [this message]
2018-08-31 9:37 ` Cyril Hrubis
2018-08-31 10:39 ` Petr Vorel
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=20180831084149.GA16417@rei.lan \
--to=chrubis@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).