Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Sep 2000 13:20:51 -0400
From:      "Patrick Bihan-Faou" <patrick@mindstep.com>
To:        "Boris Popov" <bp@FreeBSD.org>
Cc:        <cvs-all@freebsd.org>
Subject:   Re: cvs commit: src/sys/miscfs/nullfs null_subr.c null_vfsops.c         null_vnops.c
Message-ID:  <0dc801c02714$f43be8d0$040aa8c0@local.mindstep.com>
References:  <200009251538.IAA59645@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

----- Original Message -----
From: "Boris Popov" <bp@FreeBSD.org>
Subject: cvs commit: src/sys/miscfs/nullfs null_subr.c null_vfsops.c
null_vnops.c


> bp          2000/09/25 08:38:35 PDT
>
>   Modified files:
>     sys/miscfs/nullfs    null_subr.c null_vfsops.c null_vnops.c
>   Log:
>   Fix vnode locking bugs in the nullfs.
>   Add correct support for v_object management, so mmap() operation should
>   work properly.
>   Add support for extattrctl() routine (submitted by semenu).
>
>   At this point nullfs can be considered as functional and much more
stable.
>   In fact, it should behave as a "hard" "symlink" to underlying
filesystem.
>
>   Reviewed in general by: mckusick, dillon
>   Parts of logic obtained from: NetBSD
>
>   Revision  Changes    Path
>   1.26      +30 -10    src/sys/miscfs/nullfs/null_subr.c
>   1.40      +30 -25    src/sys/miscfs/nullfs/null_vfsops.c
>   1.42      +229 -66   src/sys/miscfs/nullfs/null_vnops.c


Any chance this would be MFC'd to RELENG_4 ?

If not how safe is it to import it manually ?


Patrick.







To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0dc801c02714$f43be8d0$040aa8c0>