From: Patrick Caulfeld <pcaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: Sanity check namelen before copying it
Date: Thu, 17 Jan 2008 10:25:28 +0000 [thread overview]
Message-ID: <478F2D18.5030303@redhat.com> (raw)
The 32/64 compatibility code in the DLM does not check the validity of
the lock name length passed into it, so it can easily overwrite memory
if the value is rubbish (as early versions of libdlm can cause with
unlock calls, it doesn't zero the field).
This patch restricts the length of the name to the amount of data
actually passed into the call.
Signed-Off-By: Patrick Caulfield <pcaulfie@redhat.com>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ppcdiff.upstream
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20080117/e4517c22/attachment.ksh>
next reply other threads:[~2008-01-17 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 10:25 Patrick Caulfeld [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 22:25 [Cluster-devel] [PATCH] dlm: Sanity check namelen before copying it 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=478F2D18.5030303@redhat.com \
--to=pcaulfie@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).