Date: Thu, 7 Oct 2010 16:27:03 +0200 From: Daichi GOTO <daichi@ongs.co.jp> To: Garrett Cooper <gcooper@freebsd.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: fcntl always fails to delete lock file, and PID is always -6464 Message-ID: <40A99AF1-8989-4121-8659-CF3E169FD2F8@ongs.co.jp> In-Reply-To: <AANLkTine%2B7_vqNjS4ztu6tSVEqaWLEAu%2B9PS-07z26PU@mail.gmail.com> References: <20101004123725.65d09b9e.daichi@ongs.co.jp> <AANLkTinZg3n3wDUzQFPv_Gq1o2hswGL3%2B4o0brmTi0-h@mail.gmail.com> <20101004144927.36822f07.daichi@ongs.co.jp> <AANLkTimVcLVdULyAAJD-_TaC5OLj%2BaZVNa=%2BSaiN6PKv@mail.gmail.com> <20101005093826.17432b1e.daichi@ongs.co.jp> <AANLkTi=w5ZAfRymSYbL6X37uyYX17J2dW8LHVcPXZ_%2Bb@mail.gmail.com> <20101005153410.598e4484.daichi@ongs.co.jp> <AANLkTin=9MKZGf7RREfcReamdJpCQ56BMn_RKy8eOU0-@mail.gmail.com> <20101005175536.a67998ae.daichi@ongs.co.jp> <AANLkTine%2B7_vqNjS4ztu6tSVEqaWLEAu%2B9PS-07z26PU@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 5, 2010, at 4:52 PM, Garrett Cooper wrote:
> On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO <daichi@ongs.co.jp> wrote:
>> On Tue, 5 Oct 2010 01:23:02 -0700
>> Garrett Cooper <gcooper@FreeBSD.org> wrote:
>>> 2010/10/4 Daichi GOTO <daichi@ongs.co.jp>:
>>>> Thanks nice test tool :) And at last I got it excepting one =
mystery!
>>>>=20
>>>> On Mon, 4 Oct 2010 20:17:08 -0700
>>>> Garrett Cooper <gcooper@FreeBSD.org> wrote:
>>>>> Following through the same process on FreeBSD...
>>>>>=20
>>>>> Window 1:
>>>>> $ ls -l /tmp/lockfile
>>>>> ls: /tmp/lockfile: No such file or directory
>>>>> $ ./test_fcntl
>>>>>=20
>>>>> Window 2:
>>>>>=20
>>>>> $ ls -l /tmp/lockfile
>>>>> -rwsr-x--- 1 garrcoop wheel 0 Oct 4 20:14 /tmp/lockfile
>>>>> $ ./test_fcntl
>>>>> test_fcntl: fcntl: Resource temporarily unavailable
>>>>=20
>>>> Just my mystery is as follow:
>>>>=20
>>>> Windows 1:
>>>> % ./test_fcntl
>>>> My pid: 43490
>>>>=20
>>>> Windows 2:
>>>> % ls -l /tmp/lockfile
>>>> -r-sr-x--- 1 daichi wheel 0 10=E6=9C=88 5 15:02 /tmp/lockfile =
<--- is it weird, isn't it?
>>>> % ./test_fcntl
>>>> test_fcntl: open: Permission denied
>>>> %
>>>>=20
>>>> Oops... What's wrong... /tmp is as follow:
>>>>=20
>>>> % mount | grep tmp
>>>> /dev/ada0s1f on /tmp (ufs, local, noatime, soft-updates)
>>>> % dumpfs /tmp | grep journal
>>>> flags soft-updates+journal
>>>> %
>>>>=20
>>>> And working scene:
>>>>=20
>>>> Windows 2:
>>>> % chmod u+w /tmp/lockfile
>>>> % ls -l /tmp/lockfile
>>>> -rwsr-x--- 1 daichi wheel 0 10=E6=9C=88 5 15:22 /tmp/lockfile
>>>> % ./test_fcntl
>>>> My pid: 43646
>>>> test_fcntl: fcntl[1]: Resource temporarily unavailable
>>>> PID=3D43490 has the lock
>>>> %
>>>=20
>>> What's your umask and what are the permissions on /tmp?
>>=20
>> % ll / | grep tmp
>> drwxrwxrwt 14 root wheel 1024 10=E6=9C=88 5 17:19 tmp
>> % umask
>> 022
>> % rm -f test
>> % touch test
>> % ll | grep test
>> -rw-r--r-- 1 daichi wheel 0 10=E6=9C=88 5 17:52 test
>> %
>=20
> The permissions look ok from my perspective, but the umask is
> different, so you might want to try my umask to make sure that your
> results match mine (and we need to check the requirements to determine
> whether or not the behavior for FreeBSD's umask syscall is correct):
>=20
> $ ls -la /tmp/ | head -n 2
> total 462686
> drwxrwxrwt 51 root wheel 11776 Oct 5 03:11 .
> $ umask
> 0022
The results are different on some users, even on the same user!
(022 and 0022 shows the same results.)
test user:
$ rm -f /tmp/lockfile
$ ./test_fcntl
My pid: 63133
^C
$ ll /tmp/lockfile
---sr----- 1 test wheel - 0 Oct 7 23:16 /tmp/lockfile*
$
daichi:
% rm -f /tmp/lockfile =20
% ./test_fcntl=20
My pid: 63140
^C
% ll /tmp/lockfile
---Sr-x--- 1 daichi wheel 0 10=E6=9C=88 7 23:17 /tmp/lockfile
%=20
But above daichi's result was ---sr----- as the same as test user.
After some operation, it turns into returing ---Sr-x---. I didn't =
remember=20
what operation did that.
root:
# rm -f /tmp/lockfile
# ./test_fcntl
My pid: 63147
^C
# ls -l /tmp/lockfile
--wSr-S--- 1 root wheel 0 Oct 7 23:20 /tmp/lockfile
#=20
It is mystery.
> Where and how is /tmp mounted (is it a real partition, what
> filesystem, etc)?
UFS+SUJ+noatime real pertition. I checked atime version, and got the =
same=20
result.
> BTW, when I change my umask to match your's I don't get the same
> results you do on my home machine:
>=20
> Window 1:
>=20
> $ umask 022
> $ ./test_fcntl
> My pid: 17353
>=20
> Window 2:
>=20
> $ ./test_fcntl
> My pid: 17356
> test_fcntl: fcntl[1]: Resource temporarily unavailable
> PID=3D17353 has the lock
> $ ls -l /tmp/lockfile
> -rwSr----- 1 gcooper wheel 0 Oct 5 07:49 /tmp/lockfile
>=20
> Just to note, the tests before were run on the RHEL 4.8 box with
> the following info, and the FreeBSD box with the following info:
>=20
> Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
> Linux sjc-lds-102 2.6.9-89.0.11.ELsmp #1 SMP Mon Aug 31 11:00:34 EDT
> 2009 x86_64 x86_64 x86_64 GNU/Linux
>=20
> FreeBSD bioshock.cisco.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1
> r211767M: Sat Aug 28 00:28:45 PDT 2010
> garrcoop@bioshock.cisco.com:/usr/obj/usr/src/sys/BIOSHOCK amd64
>=20
> The tests above were run on a FreeBSD box with the following info:
>=20
> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #9 r211309M:
> Thu Aug 19 22:50:36 PDT 2010
> root@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA amd64
>=20
> On bayonetta /tmp is SUJ backed (probably should change that
> though), and on bioshock it's not SUJ backed.
> Thanks!
> -Garrett
Still now, I couldn't find the cause of this issue, but it's ok by code =
following,
and program should set permission at creating time I guess.
fd =3D open("/tmp/lockfile", O_CREAT|O_WRONLY,0600);
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A99AF1-8989-4121-8659-CF3E169FD2F8>