In message <[EMAIL PROTECTED]>, 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
Sounds like a plan, and a quick eyeball of the patch shows no trouble.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message