From: Christoph Hellwig <hch@infradead.org>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: kernel@bonin.ca, aia21@cantab.net, linux-kernel@vger.kernel.org
Subject: Re: Loop devices under NTFS
Date: Tue, 27 Aug 2002 14:15:30 +0100 [thread overview]
Message-ID: <20020827141530.A25956@infradead.org> (raw)
In-Reply-To: <200208271240.FAA04753@adam.yggdrasil.com>; from adam@yggdrasil.com on Tue, Aug 27, 2002 at 05:40:52AM -0700
On Tue, Aug 27, 2002 at 05:40:52AM -0700, Adam J. Richter wrote:
> There are only a few file systems that provide writable files
> without aops->{prepare,commit}_write. I think they are just tmpfs,
> ntfs and intermezzo. If all file systems that provided writable files
> could be expected to provide {prepare,commit}_write, I could eliminate
> the file_ops->{read,write} code from loop.c.
This is the wrong level of abstraction. There is no reason why a filesystem
has to use the pagecache at all.
Note that there is a more severe bug in loop.c: it's abuse of
do_generic_file_read.
next prev parent reply other threads:[~2002-08-27 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 12:40 Adam J. Richter
2002-08-27 12:46 ` Anton Altaparmakov
2002-08-27 13:15 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 11:00 Adam J. Richter
2002-08-29 11:27 ` Anton Altaparmakov
2002-08-29 15:16 ` Jari Ruusu
2002-08-28 9:17 Adam J. Richter
2002-08-28 1:49 Adam J. Richter
2002-08-28 8:36 ` Urban Widmark
2002-08-28 1:06 Adam J. Richter
2002-08-28 15:50 ` Andre Bonin
2002-08-28 16:41 ` Christoph Hellwig
2002-08-27 23:42 Adam J. Richter
2002-08-27 23:59 ` Christoph Hellwig
2002-08-27 13:53 Adam J. Richter
2002-08-27 17:04 ` Christoph Hellwig
2002-08-27 17:26 ` Jan Harkes
2002-08-27 13:23 Adam J. Richter
2002-08-27 13:27 ` Christoph Hellwig
2002-08-27 4:48 Andre Bonin
2002-08-27 9:17 ` Anton Altaparmakov
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=20020827141530.A25956@infradead.org \
--to=hch@infradead.org \
--cc=adam@yggdrasil.com \
--cc=aia21@cantab.net \
--cc=kernel@bonin.ca \
--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
all inboxes | Powered by JetHome®