linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Juan J. Quintela" <quintela@fi.udc.es>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: lkml <linux-kernel@vger.rutgers.edu>, linux-mm@kvack.org
Subject: Re: PATCH: Rewrite of truncate_inode_pages (WIP)
Date: 31 May 2000 14:13:03 +0200	[thread overview]
Message-ID: <ytt7lcaex4g.fsf@serpe.mitica> (raw)
In-Reply-To: Trond Myklebust's message of "31 May 2000 10:58:42 +0200"

>>>>> "trond" == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

>>>>> " " == Juan J Quintela <quintela@fi.udc.es> writes:
>> This patch does:

>> - defines a new function: discard_buffer, it will lock the buffer
>> (waiting if needed) and remove the buffer from all the
>> queues.  It is like unmap_buffer, but makes sure that we
>> don't do any IO and that we remove the buffer from all the
>> lists.

>> - defines a new function: block_destroy_buffers: it is a mix of
>> block_flushpage and do_try_to_free_pages.  It will make all
>> the buffers in that page disappear calling discard_buffer.
>> Notice the way that we iterate through all the buffer heads.
>> I think that it is not racy, but I would like to hear
>> comments from people than know more about buffer heads
>> handling.

>> - I change invalidate_inode_pages (again).  Now block_destroy_buffers
>> can wait, then we are *civilized* citizens and drop any lock
>> that we have before call that block_destroy_buffers, and
>> reaquire later.

trond> This is a bug! invalidate_inode_pages() is not supposed to invalidate
trond> pending writes. It is only supposed to invalidate the page cache.

OK, the problem here is that __remove_inode_pages needs to be called
with page->buffers==NULL.  What do you suggest to obtain that?

We don't invalidate the pending write, we only *make sure* that the
buffers of the page are freed, i.e. We wait for the writes to finish.

trond> Also, it is pointless to add block device-specific code to that
trond> particular function since no block devices actually use it.

Ok, tell me *the* correct way of doing that.  We need to make sere
that __remove_inode_page is called with page->buffers == NULL.  It is
ok for you:
   if(page->buffers)
        BUG();

If we don't make a test like that (or the *actual* one), we left pages
in the page cache which contents are invalid, and when shrink_mmap try
to free that page, it would write that buffers (buffers that are in
the invalidated part).

Thanks a lot for the comments.

Later,Juan.


-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-05-31 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-30  1:29 Juan J. Quintela
2000-05-30  1:52 ` Juan J. Quintela
2000-05-31  8:58 ` Trond Myklebust
2000-05-31 12:13   ` Juan J. Quintela [this message]
2000-05-31 12:30     ` Trond Myklebust
2000-05-31 15:03       ` Juan J. Quintela

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=ytt7lcaex4g.fsf@serpe.mitica \
    --to=quintela@fi.udc.es \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=trond.myklebust@fys.uio.no \
    /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