From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SYYcu-0006F4-4g for ltp-list@lists.sourceforge.net; Sun, 27 May 2012 08:15:00 +0000 Received: from [222.73.24.84] (helo=song.cn.fujitsu.com) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SYYcs-0000kw-QC for ltp-list@lists.sourceforge.net; Sun, 27 May 2012 08:15:00 +0000 Message-ID: <4FC1E248.6040008@cn.fujitsu.com> Date: Sun, 27 May 2012 16:14:00 +0800 From: Wanlong Gao MIME-Version: 1.0 References: <4FC1D8C5.4050804@cn.fujitsu.com> In-Reply-To: Subject: Re: [LTP] [PATCH] Fix the fork/11-1 conformance testcase Reply-To: gaowanlong@cn.fujitsu.com List-Id: Linux Test Project General Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-list-bounces@lists.sourceforge.net To: Garrett Cooper Cc: LTP list On 05/27/2012 04:00 PM, Garrett Cooper wrote: > On Sun, May 27, 2012 at 12:33 AM, Wanlong Gao wrote: >> On 05/26/2012 10:15 PM, Garrett Cooper wrote: >> >>> The testcase tests to see whether or not locks are successfully >>> inherited across forking processes, as the requirements for fork state >>> that they should not be. The problem is that the test tests the negative >>> case for ftrylockfile (!= 0) instead of the positive case, which creates >> >> The ftrylockfile() function returns zero for success (the lock was obtained), >> and nonzero for failure. >> So I think the origin is right. > > My description might be wrong, but the fix is right. ftrylockfile > should fail in the testcase (not succeed) because the file lock isn't > owned by the forked process. It succeeds simply because the delay is But on my system ftrylockfile() always return 0, and the test PASSED. and with your patch, it fails. Thanks, Wanlong Gao > long enough on some platforms. I could check and ensure that EAGAIN > (or the POSIX prescribed error) occurs if this occurs instead in the > implicit else case. > Thanks! > -Garrett > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list