From: Zach Brown <zach.brown@oracle.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [RFC] page lock ordering and OCFS2
Date: Tue, 18 Oct 2005 10:25:51 -0700 [thread overview]
Message-ID: <4355301F.9020003@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510180916420.7514@hermes-1.csi.cam.ac.uk>
Anton Altaparmakov wrote:
> What I would ask is why does the above dlm thread need to hold the
> data_lock duing truncate_inode_pages?
I hope the mail I just sent made that a little more clear.
> and repeat truncate_inode_pages, etc. Eventually it will succeed. And no
> need for nasty VFS patch you are proposing...
Yeah, this also came to me this morning in the shower :) There are some
hard cases because these are actually read-write locks, but it might be
doable. We're discussing it.
> no pages left, unless there is an overeager read process at work on that
> mapping at the same time.
I fear that it'll be pretty easy to get bad capture effects, but maybe
that's ok. We'll see.
- z
next prev parent reply other threads:[~2005-10-18 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 22:20 [RFC] page lock ordering and OCFS2 Zach Brown
2005-10-17 23:17 ` Andrew Morton
2005-10-18 0:40 ` Zach Brown
2005-10-18 1:24 ` Andrew Morton
2005-10-18 8:23 ` Anton Altaparmakov
2005-10-18 17:25 ` Zach Brown [this message]
2005-10-18 17:14 ` Zach Brown
2005-10-21 17:43 ` Zach Brown
2005-10-21 17:57 ` Christoph Hellwig
2005-10-21 20:36 ` Zach Brown
2005-10-21 20:59 ` Andrew Morton
2005-10-21 21:57 ` Zach Brown
2005-10-25 0:03 ` Zach Brown
2005-10-21 17:58 ` Andrew Morton
2005-10-21 20:32 ` Zach Brown
2005-10-17 23:37 ` Badari Pulavarty
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=4355301F.9020003@oracle.com \
--to=zach.brown@oracle.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--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