From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs incore.h inode.c op ...
Date: 2 Aug 2006 17:21:20 -0000 [thread overview]
Message-ID: <20060802172120.24384.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2006-08-02 17:21:20
Modified files:
gfs-kernel/src/gfs: incore.h inode.c ops_address.c
Log message:
This is a fix for bugzilla bz 164499 (Unable to mount loopback
images from mounted GFS partition). The previous fix had a
problem where any writes to files in the file system would
cause the problem to reappear. For more details see:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=164499
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/incore.h.diff?cvsroot=cluster&r1=1.25&r2=1.26
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/inode.c.diff?cvsroot=cluster&r1=1.24&r2=1.25
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_address.c.diff?cvsroot=cluster&r1=1.12&r2=1.13
--- cluster/gfs-kernel/src/gfs/incore.h 2006/07/10 23:22:34 1.25
+++ cluster/gfs-kernel/src/gfs/incore.h 2006/08/02 17:21:19 1.26
@@ -617,6 +617,7 @@
unsigned int i_greedy; /* The amount of time to be greedy */
unsigned long i_last_pfault; /* The time of the last page fault */
+ struct address_space_operations gfs_file_aops;
};
/*
--- cluster/gfs-kernel/src/gfs/inode.c 2006/07/10 23:22:34 1.24
+++ cluster/gfs-kernel/src/gfs/inode.c 2006/08/02 17:21:19 1.25
@@ -191,7 +191,9 @@
if (ip->i_di.di_type == GFS_FILE_REG) {
tmp->i_op = &gfs_file_iops;
tmp->i_fop = &gfs_file_fops;
- tmp->i_mapping->a_ops = &gfs_file_aops;
+ memcpy(&ip->gfs_file_aops, &gfs_file_aops,
+ sizeof(struct address_space_operations));
+ tmp->i_mapping->a_ops = &ip->gfs_file_aops;
} else if (ip->i_di.di_type == GFS_FILE_DIR) {
tmp->i_op = &gfs_dir_iops;
tmp->i_fop = &gfs_dir_fops;
--- cluster/gfs-kernel/src/gfs/ops_address.c 2006/07/14 18:44:42 1.12
+++ cluster/gfs-kernel/src/gfs/ops_address.c 2006/08/02 17:21:19 1.13
@@ -327,7 +327,7 @@
/* it's okay to do buffered writes without locking through sendfile. */
/* This is a kludge to get around the problem with loop.c because */
/* the upstream community rejected my changes to loop.c. */
- gfs_file_aops.commit_write = gfs_commit_write;
+ ip->gfs_file_aops.commit_write = gfs_commit_write;
if (gfs_assert_warn(sdp, gfs_glock_is_locked_by_me(ip->i_gl)))
return -ENOSYS;
@@ -397,6 +397,7 @@
goto fail;
}
+ ip->gfs_file_aops.commit_write = NULL;
return 0;
fail:
next reply other threads:[~2006-08-02 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 17:21 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-10 18:35 [Cluster-devel] cluster/gfs-kernel/src/gfs incore.h inode.c op rpeterso
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=20060802172120.24384.qmail@sourceware.org \
--to=rpeterso@sourceware.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).