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?
Date: Sat, 3 Jan 2004 18:57:12 +0000 [thread overview]
Message-ID: <20040103185712.GV4176@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <bt71ip$cer$1@gatekeeper.tmr.com>
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.
next prev parent reply other threads:[~2004-01-03 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 19:40 Should struct inode be made available to userspace? Mariusz Mazur
2003-12-29 19:57 ` viro
2004-01-03 18:39 ` Bill Davidsen
2004-01-03 18:57 ` viro [this message]
2004-01-04 5:43 ` Bill Davidsen
2004-01-04 5:45 ` Jeff Woods
2004-01-04 6:28 ` viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040103185712.GV4176@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox