linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Nick Piggin <npiggin@suse.de>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, mhalcrow@us.ibm.com,
	phillip@hellewell.homeip.net, sfrench@samba.org
Subject: Re: [rfc][patch 3/5] afs: new aops
Date: Tue, 13 Nov 2007 10:56:25 +0000	[thread overview]
Message-ID: <18637.1194951385@redhat.com> (raw)
In-Reply-To: <20071113004459.GE30650@wotan.suse.de>

Nick Piggin <npiggin@suse.de> wrote:

> It takes a pagecache page, yes. If you follow convention, you use
> PAGE_CACHE_SIZE for that guy. You don't have to allow PAGE_CACHE_SIZE !=
> PAGE_SIZE, and if all the rest of your code is in units of PAGE_SIZE, then
> obviously my changing of just the one unit is even more confusing than
> the current arrangement ;)

The problem is that the code called assumes that the struct page * argument
points to a single page, not an array of pages as would presumably be the case
if PAGE_CACHE_SIZE > PAGE_SIZE.  If I should allow for an array of pages then
the lower functions (specifically afs_deliver_fs_fetch_data()) need to change,
and until that time occurs, the assertion *must* remain as it is now.  It
defends the lower functions against being asked to do something they weren't
designed to do.

So: you may not change the assertion unless you also fix the lower functions.

David

  parent reply	other threads:[~2007-11-13 10:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  7:12 [rfc][patches] remove ->prepare_write Nick Piggin
2007-11-12  7:13 ` [rfc][patch 1/5] ecryptfs new aops Nick Piggin
2007-11-12  7:14 ` [rfc][patch 2/5] cifs: " Nick Piggin
2007-11-12  7:14 ` [rfc][patch 3/5] afs: " Nick Piggin
2007-11-12  7:20 ` [rfc][patch 4/5] rd: rewrite rd Nick Piggin
2007-11-12  7:23 ` [rfc][patch 5/5] remove prepare_write Nick Piggin
2007-11-12 15:29 ` [rfc][patch 3/5] afs: new aops David Howells
2007-11-13  0:15   ` Nick Piggin
2007-11-13  0:30   ` David Howells
2007-11-13  0:44     ` Nick Piggin
2007-11-13 10:56     ` David Howells [this message]
2007-11-14  4:24       ` Nick Piggin
2007-11-14 12:18       ` David Howells
2007-11-14 15:18         ` Nick Piggin
2007-11-14 15:57         ` David Howells
2007-11-14 21:32           ` Nick Piggin
2007-11-15 12:15           ` David Howells
2007-11-15 21:37             ` Nick Piggin

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=18637.1194951385@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=npiggin@suse.de \
    --cc=phillip@hellewell.homeip.net \
    --cc=sfrench@samba.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;
as well as URLs for NNTP newsgroup(s).