Date: Sat, 3 Jan 2004 18:57:12 +0000
From: viro@parcelfarce.linux.theplanet.co.uk
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Should struct inode be made available to userspace?
Message-ID: <20040103185712.GV4176@parcelfarce.linux.theplanet.co.uk>
References: <200312292040.00409.mmazur@kernel.pl> <20031229195742.GL4176@parcelfarce.linux.theplanet.co.uk> <bt71ip$cer$1@gatekeeper.tmr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bt71ip$cer$1@gatekeeper.tmr.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1074
Lines: 23

On Sat, Jan 03, 2004 at 01:39:41PM -0500, Bill Davidsen wrote:
> viro@parcelfarce.linux.theplanet.co.uk wrote:
> 
> >struct inode and structures containing it should not be used outside of 
> >kernel.
> >Moreover, foo_fs.h should be seriously trimmed down and everything _not_
> >useful outside of kernel should be taken into fs/foo/*; other kernel code
> >also doesn't give a fsck for that stuff, so it should be private to 
> >filesystem
> >instead of polluting include/linux/*.
> 
> Moving the definitions is fine, but some user programs, like backup 
> programs, do benefit from direct interpretation of the inode. Clearly 
> that's not a normal user program, but this information is not only 
> useful inside the kernel.

No, they do not.  They care about on-disk structures, not the in-core
ones fs driver happens to build.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/