From: Andreas Dilger <adilger@clusterfs.com>
To: Dmitry Monakhov <dmonakhov@sw.ru>
Cc: Alex Tomas <alex@clusterfs.com>,
cmm@us.ibm.com, linux-ext4@vger.kernel.org
Subject: Re: delayed allocatiou result in Oops
Date: Tue, 19 Jun 2007 15:50:05 -0600 [thread overview]
Message-ID: <20070619215005.GU5181@schatzie.adilger.int> (raw)
In-Reply-To: <20070619091628.GB20172@localhost.sw.ru>
On Jun 19, 2007 13:16 +0400, Dmitry Monakhov wrote:
> But whole approach based on using PagePrivate bit and page->private
> ptr for special purposes is realy dengerous, and imho wrong,
> because avery fs-related code assume that page->private points to
> page_buffers.
This is actually a misconception. page->private can be anything. While
many fs helper routines use page->private as buffers, that only happens
when the fs itself causes those helper routines to be called. Lustre,
for example, has no buffer heads on the clients, and uses page->private
to track RPC batching information and data checksums.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-06-19 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 7:23 delayed allocatiou result in Oops Dmitriy Monakhov
2007-06-15 5:14 ` Alex Tomas
2007-06-15 23:16 ` Mingming Cao
2007-06-16 8:02 ` [PATCH] ext4:fix invariant checking in ext4_rebalance_reservation Dmitriy Monakhov
2007-06-18 21:09 ` Mingming Cao
2007-06-19 5:56 ` Dmitry Monakhov
2007-06-16 8:14 ` delayed allocatiou result in Oops Dmitriy Monakhov
2007-06-19 1:01 ` Mingming Cao
2007-06-19 7:11 ` Alex Tomas
2007-06-19 9:16 ` Dmitry Monakhov
2007-06-19 9:36 ` Alex Tomas
2007-06-19 21:50 ` Andreas Dilger [this message]
2007-06-19 16:23 ` Mingming Cao
2007-06-19 16:47 ` Aneesh Kumar K.V
2007-06-20 8:15 ` Alex Tomas
2007-06-20 23:46 ` Mingming Cao
2007-06-21 4:50 ` Dmitry Monakhov
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=20070619215005.GU5181@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=dmonakhov@sw.ru \
--cc=linux-ext4@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