Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 May 2010 19:05:15 +0300
From:      Efstratios Karatzas <gpf.kira@gmail.com>
To:        John Baldwin <jhb@freebsd.org>
Cc:        Perforce Change Reviews <perforce@freebsd.org>, Efstratios Karatzas <gpf@freebsd.org>
Subject:   Re: PERFORCE change 178714 for review
Message-ID:  <AANLkTimg6sjf1ymn969GKhW681PosQSOPbvbP3Ph3PiC@mail.gmail.com>
In-Reply-To: <201005250858.24659.jhb@freebsd.org>
References:  <201005241406.o4OE6v5B051548@repoman.freebsd.org> <201005250858.24659.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 25, 2010 at 3:58 PM, John Baldwin <jhb@freebsd.org> wrote:
> On Monday 24 May 2010 10:06:57 am Efstratios Karatzas wrote:
>> http://p4web.freebsd.org/@@178714?ac=3D10
>>
>> Change 178714 by gpf@gpf_desktop on 2010/05/24 14:06:34
>>
>> =C2=A0 =C2=A0 =C2=A0 * the second parameter from VOP_VPTOCNP() should be=
 vdrop()ed after
>> =C2=A0 =C2=A0 =C2=A0 the call - done
>> =C2=A0 =C2=A0 =C2=A0 * dont really need exclusive locks; now I use share=
d locks
>> =C2=A0 =C2=A0 =C2=A0 * dir_ilookup() still only works for UFS, added a c=
heck so that the
>> =C2=A0 =C2=A0 =C2=A0 function will return if the fs is not ufs
>>
>> Affected files ...
>>
>> .. //depot/projects/soc2010/gpf_audit/vn_fullpath_nocache.c#3 edit
>>
>> Differences ...
>>
>> =3D=3D=3D=3D //depot/projects/soc2010/gpf_audit/vn_fullpath_nocache.c#3 =
(text+ko) =3D=3D=3D=3D
>>
>> @@ -75,11 +75,18 @@
>> =C2=A0 =C2=A0 =C2=A0 KASSERT("dvp !=3D NULL", "dir_ilookup: dvp =3D=3D N=
ULL");
>> =C2=A0 =C2=A0 =C2=A0 KASSERT("name !=3D NULL", "dir_ilookup: name =3D=3D=
 NULL");
>>
>> + =C2=A0 =C2=A0 /* XXXgpf: temporary, must be a better way to check this=
 than f_type or f_fstypename */
>> + =C2=A0 =C2=A0 if (strcmp(vp->v_mount->mnt_stat.f_fstypename, "ufs")) {
>> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 uprintf("only ufs supported\=
n");
>> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 return 1;
>> + =C2=A0 =C2=A0 }
>> +
>
> The normal way to handle something like this is by moving the
> filesystem-specific functionality into a new VOP. =C2=A0Alternatively, th=
e mount
> point could grow a new flag (such as MNTK_MPSAFE or MNTK_LOOKUP_SHARED) t=
o
> indicate that a specific mount supports an optional feature or capability=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimg6sjf1ymn969GKhW681PosQSOPbvbP3Ph3PiC>