From: wengang wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [BUGFIX][OCFS2 1/1] inode truncating
Date: Mon, 30 Jun 2008 16:57:19 +0800 [thread overview]
Message-ID: <48689FEF.6040504@oracle.com> (raw)
/an ocfs2 bug:
a truncate races with ocfs2_get_block(...,0).
1) 'dd' is doing a truncate, clearing the page cache and reset inode size./
/2) between clearing page cache and resizing inode, a read comes and
create a /
/new page and insert it to page cache./
/3) the read(from `cat`) set buffer head in the new page as mapped but
doesn't increase / /ip_mmu_private in ocfs2_get_block() because it's a
read./
/4) a write from 'dd' matches the page that the read created. because
the buffer /
/heads are already mapped, it doesn't call ocfs2_get_block. the
ip_mmu_private /
/keeps unchanged since last write./
/5) in cont_prepare_write() it dead loops since bytes(ip_mmu_private) is
not /
/increased in last prepare write./
BUG is described in
s://bug.oraclecorp.com/pls/bug/webbug_print.show?c_rptno=7183894.
solution:
/1) moves the clearing of page cache truncate_inode_pages() from
ocfs2_truncate_file() to/
/ocfs2_set_inode_size() after resizing inode size and i_blocks./
/2) in ocfs2_get_block(), add checks on iblock >= inode->i_blocks. if
true, return -EIO.
3) //a kernel bug fix is needed for 2.6.9 kernel.
//see https://bugzilla.redhat.com/show_bug.cgi?id=453359/
aops.c | 6 ++++++
file.c | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ocfs2_truncate.patch
Type: text/x-patch
Size: 1146 bytes
Desc: not available
Url : http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20080630/b27b78c5/attachment.bin
next reply other threads:[~2008-06-30 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 8:57 wengang wang [this message]
2008-06-30 9:04 ` [Ocfs2-devel] [BUGFIX][OCFS2 1/1] inode truncating wengang wang
2008-07-01 3:24 ` Sunil Mushran
2008-07-01 3:53 ` wengang wang
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=48689FEF.6040504@oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.