All of lore.kernel.org
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, STABLE2, updated. cluster-2.03.02-7-ga6b6a30
Date: 13 May 2008 19:08:54 -0000	[thread overview]
Message-ID: <20080513190854.7210.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=a6b6a30358fd5e247a37e2fe493ef6a683174b66

The branch, STABLE2 has been updated
       via  a6b6a30358fd5e247a37e2fe493ef6a683174b66 (commit)
      from  edd597845e68e9826907ec1e23692e1fc394e9a4 (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 a6b6a30358fd5e247a37e2fe493ef6a683174b66
Author: David Teigland <teigland@redhat.com>
Date:   Tue May 13 14:04:51 2008 -0500

    gfs_controld: ignore write(2) return value on plock dev
    
    bz 446128
    
    When plocks originate from nfs clients, the kernel mistakenly
    returns 0 instead of the number of bytes written to the plock
    device on write(2).  Don't spam /var/log/messages with errors
    reporting a bad return value from write(2).
    
    Signed-off-by: David Teigland <teigland@redhat.com>

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

Summary of changes:
 group/gfs_controld/plock.c |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/group/gfs_controld/plock.c b/group/gfs_controld/plock.c
index 42890df..beedf42 100644
--- a/group/gfs_controld/plock.c
+++ b/group/gfs_controld/plock.c
@@ -771,12 +771,8 @@ static int add_waiter(struct mountgroup *mg, struct resource *r,
 static void write_result(struct mountgroup *mg, struct gdlm_plock_info *in,
 			 int rv)
 {
-	int err;
-
 	in->rv = rv;
-	err = write(control_fd, in, sizeof(struct gdlm_plock_info));
-	if (err != sizeof(struct gdlm_plock_info))
-		log_error("plock result write err %d errno %d", err, errno);
+	write(control_fd, in, sizeof(struct gdlm_plock_info));
 }
 
 static void do_waiters(struct mountgroup *mg, struct resource *r)


hooks/post-receive
--
Cluster Project



             reply	other threads:[~2008-05-13 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 19:08 teigland [this message]
2008-05-13 20:01 ` [Cluster-devel] Cluster Project branch, STABLE2, updated. cluster-2.03.02-7-ga6b6a30 Steven Whitehouse
2008-05-13 20:13   ` David Teigland
2008-05-14  8:56     ` Steven Whitehouse
2008-05-14 13:33       ` David Teigland

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