From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Ramit Bhalla <ramit.bhalla@wipro.com>
Cc: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: Kernel Mode File Operations Wrappers
Date: Mon, 18 Aug 2003 11:31:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308181120190.15831@chaos> (raw)
In-Reply-To: <52C85426D39B314381D76DDD480EEE0CF5FCAB@blr-m3-msg.wipro.com>
On Mon, 18 Aug 2003, Ramit Bhalla wrote:
> Hi,
>
> I've written a file that provides wrappers for kernel mode file operations
> (using existing filp_xx and supporting operations).
> This provides support for opening/closing/reading/writing/seeking/formatting
> etc operations. This should help kernel mode developers with fs
> operations in their kernel drivers/modules.
>
> It helps simplify kernel mode file operations and takes care of
> various issues (which one can forget at times) like handling
> the FS registers , uid and gid. It exposes kernel mode file
> operations in a way that are very similar to user mode
> operations like
> fopen, fclose, fseek etc.
>
> I have tested it on a few systems and it appears to be working great.
>
> Hope this finds it's way into the linux kernel :)
>
> Ramit.
>
This appears to be a cruel joke! From whom does the kernel steal
'current' when obtaining a file descriptor? And, how-come there
is a CR/LF sequence for each end-of-line? Is this some DOS program?
If there are any developers using file-access in their modules,
as stated above, that stuff should never be included in the kernel.
If those persons want to permanently damage the OS by doing same,
then they can do whatever in their own trees.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
prev parent reply other threads:[~2003-08-18 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 14:37 Kernel Mode File Operations Wrappers Ramit Bhalla
2003-08-18 15:31 ` Richard B. Johnson [this message]
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=Pine.LNX.4.53.0308181120190.15831@chaos \
--to=root@chaos.analogic.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ramit.bhalla@wipro.com \
/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;
as well as URLs for NNTP newsgroup(s).