Date: Mon, 23 Apr 2007 16:25:42 -0700 From: "Howard Su" <howard0su@gmail.com> To: "Kostik Belousov" <kostikbel@gmail.com> Cc: arch@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: move audit/priviliage check into VFS Message-ID: <f126fae00704231625q258636c9o13a35a5d1414b7be@mail.gmail.com> In-Reply-To: <20070423115042.GF2052@deviant.kiev.zoral.com.ua> References: <f126fae00704221458k41e6b758ld99486f6e837939@mail.gmail.com> <20070423115042.GF2052@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/23/07, Kostik Belousov <kostikbel@gmail.com> wrote: > On Sun, Apr 22, 2007 at 02:58:30PM -0700, Howard Su wrote: > Quota code (ufs/ufs/ufs_quota.c) is mostly filesystem-independent, it > only require particular format for the quota file, and several fields in > the ufs mount structure, as well as ufs mount interlock. The later could be > factored-out quite easily. > > On the other hand, only ufs is stuffed with hooks for the quota handling. I agree that current implementation is FS-depend. However in theory, nothing prevent you to store quota data in another FS even. We only need some API calls which expose through VFS like AllocateQuota, FreeQuota, CheckQuota. The storage part can be hide by VFS. Anyway, this is my dream. No prototyping prove it yet. > > > I would let others comment on the feasibility of factoring out permission > check code. > > What I want to point out is that some time ago UFS itself was considered > as layer with underlying implementation providing the actual structure > for the storage. At least two such implementations existed, FFS and > LFS. The LFS is long dead and removed from CVS. All that left from the > layering is several method pointers in struct ufsmount. I suspect that > current code has eroded the border between UFS and FFS. That said, I'm > not sure whether implementing tmpfs as some TMPFS under UFS layer is > possible now, but you may look at this. > Glad to know some old stuffs. Very helpful. -- -Howard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f126fae00704231625q258636c9o13a35a5d1414b7be>