From owner-freebsd-current Tue Sep 18 5:33: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id AF13A37B40D; Tue, 18 Sep 2001 05:33:00 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8ICWvv25284; Tue, 18 Sep 2001 14:32:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Maxim Sobolev Cc: chris@calldei.com, brent@rcfile.org, current@FreeBSD.ORG, hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag In-Reply-To: Your message of "Tue, 18 Sep 2001 15:09:33 +0300." <3BA7397D.A82C213@FreeBSD.org> Date: Tue, 18 Sep 2001 14:32:57 +0200 Message-ID: <25282.1000816377@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BA7397D.A82C213@FreeBSD.org>, Maxim Sobolev writes: >> How do you figure? The contents if `f_fstypename' must match >> a configured file system exactly, so it could _not_ be anything. >> To quote sys/kern/vfs_syscalls.c:mount(): > >Oh, yes, you are correct obviously (don't know what I was thinking about). In this >case, it looks like v_tag is redundant, because f_fstypename could be used instead >in a few places where v_tag is abused (the same applies to the statfs.f_type >because essentually it is the same thing as v_tag). Poul, what do you think about >it? In the meantime, I found another place in the kernel where VT_* macros are >[ab]used - it is Linuxlator, attached please find patches to fix it - please >review. Sounds like a plan, and a quick eyeball of the patch shows no trouble. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message