From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/dlm-kernel/src device.c
Date: 5 Oct 2007 10:06:25 -0000 [thread overview]
Message-ID: <20071005100625.26575.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: pcaulfield at sourceware.org 2007-10-05 10:06:24
Modified files:
dlm-kernel/src : device.c
Log message:
Don't overwrite castparam if /it/ is NULL.
Checking castaddr is wrong because it's not possible to affect that
from the userland API.
This is also consistent with the fix for bz#318061 in RHEL5.
This check-in fixes bz#318851 but TPTB will decide whether it gets included
in RHEL4.6
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm-kernel/src/device.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.24.2.11&r2=1.24.2.12
--- cluster/dlm-kernel/src/Attic/device.c 2007/09/26 13:53:20 1.24.2.11
+++ cluster/dlm-kernel/src/Attic/device.c 2007/10/05 10:06:24 1.24.2.12
@@ -1075,10 +1075,10 @@
the existing li_castaddr as that's the completion routine for
unlocks. dlm_unlock_wait() specifies a new AST routine to be
executed when the unlock completes. */
- if (kparams->castaddr) {
+ if (kparams->castaddr)
li->li_castaddr = kparams->castaddr;
+ if (kparams->castparam)
li->li_castparam = kparams->castparam;
- }
/* Have to do it here cos the lkb may not exist after
* dlm_unlock() */
next reply other threads:[~2007-10-05 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 10:06 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 8:45 [Cluster-devel] cluster/dlm-kernel/src device.c pcaulfield
2007-10-09 7:24 pcaulfield
2007-09-26 13:53 pcaulfield
2007-09-12 8:40 pcaulfield
2006-08-14 21:13 teigland
2006-08-14 21:11 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=20071005100625.26575.qmail@sourceware.org \
--to=pcaulfield@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.