From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, RHEL5, updated. cmirror_1_1_15-18-g0484ef9
Date: 24 Mar 2008 21:28:46 -0000 [thread overview]
Message-ID: <20080324212846.6577.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=0484ef93e8d09313f8f110d23c2a6a6b4aca2f60
The branch, RHEL5 has been updated
via 0484ef93e8d09313f8f110d23c2a6a6b4aca2f60 (commit)
from d3f69f52ce9c48a7abd4fb89efc3897aac9bb1c4 (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 0484ef93e8d09313f8f110d23c2a6a6b4aca2f60
Author: Christine Caulfield <ccaulfie@redhat.com>
Date: Thu Mar 13 16:44:00 2008 +0000
[DLM] Don't segfault if lvbptr is NULL
Calling dlm_lock* with LKF_VALBLK and sb_lvbptr set
to NULL could cause libdlm to segfault.
Now it returns -1/EINVAL
Signed-off-by: Christine Caulfield <ccaulfie@redhat.com>
-----------------------------------------------------------------------
Summary of changes:
dlm/lib/libdlm.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/dlm/lib/libdlm.c b/dlm/lib/libdlm.c
index 0612d09..2bdbb0f 100644
--- a/dlm/lib/libdlm.c
+++ b/dlm/lib/libdlm.c
@@ -889,6 +889,11 @@ static int ls_lock(dlm_lshandle_t ls,
return -1;
}
+ if (flags & LKF_VALBLK && !lksb->sb_lvbptr) {
+ errno = EINVAL;
+ return -1;
+ }
+
if (kernel_version.version[0] == 5)
return ls_lock_v5(ls, mode, lksb, flags, name, namelen, parent,
astaddr, astarg, bastaddr);
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-03-24 21:28 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=20080324212846.6577.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.