linux-kernel - Re: [lkp] [af_unix] 039b21aaee: otc_kernel_qa-ts_ltp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 04 Jan 2016 13:06:09 +0000
From:	Rainer Weikusat <rweikusat@...ileactivedefense.com>
To:	kernel test robot <ying.huang@...ux.intel.com>
Cc:	Rainer Weikusat <rweikusat@...ileactivedefense.com>, lkp@...org,
	LKML <linux-kernel@...r.kernel.org>,
	Dmitry Vyukov <dvyukov@...gle.com>,
	0day robot <fengguang.wu@...el.com>
Subject: Re: [lkp] [af_unix] 039b21aaee: otc_kernel_qa-ts_ltp_ddt.bind01.fail

kernel test robot <ying.huang@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/