From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/dlm-kernel/src device.c
Date: 26 Sep 2007 13:53:21 -0000 [thread overview]
Message-ID: <20070926135321.26156.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: pcaulfield at sourceware.org 2007-09-26 13:53:20
Modified files:
dlm-kernel/src : device.c
Log message:
Don't overwrite castparam if there is no new ast routine to go with it.
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.10&r2=1.24.2.11
--- cluster/dlm-kernel/src/Attic/device.c 2007/09/12 08:40:09 1.24.2.10
+++ cluster/dlm-kernel/src/Attic/device.c 2007/09/26 13:53:20 1.24.2.11
@@ -1069,15 +1069,16 @@
}
li->li_user_lksb = kparams->lksb;
- li->li_castparam = kparams->castparam;
li->li_cmd = cmd;
/* dlm_unlock() passes a 0 for castaddr which means don't overwrite
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;
+ li->li_castparam = kparams->castparam;
+ }
/* Have to do it here cos the lkb may not exist after
* dlm_unlock() */
next reply other threads:[~2007-09-26 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 13:53 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-10-05 10:06 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=20070926135321.26156.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.