linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Rajaram Suresh Gaunker <rajarams1@rediffmail.com>
Cc: kernelnewbies@nl.linux.org, linux-fsdevel@vger.kernel.org
Subject: Re: which  function  writes to the disk
Date: Wed, 5 Mar 2003 12:54:00 -0500	[thread overview]
Message-ID: <20030305175400.GE21465@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <20030305072513.31413.qmail@webmail6.rediffmail.com>

On Wed, Mar 05, 2003 at 07:25:13AM -0000, Rajaram Suresh Gaunker wrote:
> which functions writes to the disk in file system?
> 
> how can i know which user wants to write to disk, or which user 
> has called the system call?

That is a little difficult, last time I looked, writes were just marking
the memory page dirty. At some point there is this kernel flush daemon
that wanders by, notices that the page is dirty and kicks off the actual
IO.

In the mean time several users might have written to the same page
before IO has even started which makes it unclear which user has
permission to write. Will all valid writes fail if one user's
permissions have expired? Or will we allow an user's writes to
succeed just because he is piggybacking on the valid writers.

> user registers his key by using a system call which i'm 
> providing he can also unregister itself using a system call
> 
> the key for each user is stored in kernel when we are writing the 
> data to file of user we will encrypt using owners key

You might want to google for 'cryptfs', 'cfs', and 'tcfs'.

Jan


      reply	other threads:[~2003-03-05 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  7:25 which function writes to the disk Rajaram Suresh Gaunker
2003-03-05 17:54 ` Jan Harkes [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=20030305175400.GE21465@delft.aura.cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rajarams1@rediffmail.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).