All of lore.kernel.org
 help / color / mirror / Atom feed
From: adas@sourceware.org <adas@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, RHEL47, updated. gfs-kernel_2_6_9_76-54-g10a84a8
Date: 9 May 2008 17:17:29 -0000	[thread overview]
Message-ID: <20080509171729.9331.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".

http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3

The branch, RHEL47 has been updated
       via  10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3 (commit)
      from  c9d8820962da727dcf4e2edfd755c33ce5b41b6b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3
Author: Abhijith Das <adas@redhat.com>
Date:   Fri May 9 12:00:05 2008 -0500

    gfs-kernel: Workaround fix for bz 444912 (gfs_glock_is_locked_by_me problem)
    
    This one-line fix, removes the assert warning. The behavior of the code is unchanged except that the assert warnings will no longer appear in the logs. This warning is tripped through the madvise syscall where control reaches the readpage function without the inode glock being held. We return -ENOSYS in such a case, disabling the madvise syscall.
    
    A more elegant fix for RHEL5 gfs that supports the madvise syscall (bz 429343) could not be ported to RHEL4 because AOP_TRUNCATED_PAGE is not available in RHEL4.

-----------------------------------------------------------------------

Summary of changes:
 gfs-kernel/src/gfs/ops_address.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/gfs-kernel/src/gfs/ops_address.c b/gfs-kernel/src/gfs/ops_address.c
index af5b3b3..fb17133 100644
--- a/gfs-kernel/src/gfs/ops_address.c
+++ b/gfs-kernel/src/gfs/ops_address.c
@@ -283,7 +283,7 @@ gfs_readpage(struct file *file, struct page *page)
 
 	atomic_inc(&sdp->sd_ops_address);
 
-	if (gfs_assert_warn(sdp, gfs_glock_is_locked_by_me(ip->i_gl))) {
+	if (!gfs_glock_is_locked_by_me(ip->i_gl)) {
 		unlock_page(page);
 		return -ENOSYS;
 	}


hooks/post-receive
--
Cluster Project



                 reply	other threads:[~2008-05-09 17:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080509171729.9331.qmail@sourceware.org \
    --to=adas@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 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.