From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: Rainer Weikusat <rweikusat@mobileactivedefense.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [af_unix] 039b21aaee: otc_kernel_qa-ts_ltp_ddt.bind01.fail
Date: Mon, 04 Jan 2016 13:06:09 +0000 [thread overview]
Message-ID: <87mvslo5oe.fsf@doppelsaurus.mobileactivedefense.com> (raw)
In-Reply-To: <87poxim7uu.fsf@yhuang-dev.intel.com> (kernel test robot's message of "Mon, 04 Jan 2016 09:49:45 +0800")
kernel test robot <ying.huang@linux.intel.com> writes:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux Rainer-Weikusat/af_unix-Fix-splice-bind-deadlock/20151228-041437
> commit 039b21aaee6515d0197e26321204f319b4ea6e9e ("af_unix: Fix splice-bind deadlock")
>
> The commit failed for the bind01 test case of LTP syscalls test suite.
Judging from the bind01 test case code, about the only useful
information available in this message,
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/bind/bind01.c
(and even that only indirectly), this ought the be error in the original
patch where -EEXIST from kern_path_create isn't translated to
-EADDRINUSE. This is fixed in the patch I sent yesterday, tested via
highly unsophisticated
perl -MSocket <<'TT'
socket($sk, AF_UNIX, SOCK_DGRAM, 0);
bind($sk, sockaddr_un("."));
print "$!\n"
TT
prev parent reply other threads:[~2016-01-04 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 1:49 kernel test robot
2016-01-04 13:06 ` Rainer Weikusat [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=87mvslo5oe.fsf@doppelsaurus.mobileactivedefense.com \
--to=rweikusat@mobileactivedefense.com \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@linux.intel.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
Powered by JetHome