From: mbroz@sourceware.org <mbroz@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/mm/memlock.c
Date: 6 Mar 2011 16:47:44 -0000 [thread overview]
Message-ID: <20110306164744.13366.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz at sourceware.org 2011-03-06 16:47:43
Modified files:
. : WHATS_NEW
lib/mm : memlock.c
Log message:
Fix hardcoded page size, fixing test fails with 8k page and new kernel.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1935&r2=1.1936
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/mm/memlock.c.diff?cvsroot=lvm2&r1=1.35&r2=1.36
--- LVM2/WHATS_NEW 2011/03/05 12:14:00 1.1935
+++ LVM2/WHATS_NEW 2011/03/06 16:47:43 1.1936
@@ -1,5 +1,6 @@
Version 2.02.85 -
===================================
+ Use system page size and not hardcoded value in locking code check.
Fix reading of released memory for printing segment type.
Fix syslog initialisation in clvmd to respect lvm.conf setting.
Fix possible overflow in maximum stripe size and physical extent size.
--- LVM2/lib/mm/memlock.c 2011/02/18 14:51:04 1.35
+++ LVM2/lib/mm/memlock.c 2011/03/06 16:47:43 1.36
@@ -344,7 +344,7 @@
dm_free(_maps_buffer);
_maps_buffer = NULL;
if (_mstats < unlock_mstats) {
- if ((_mstats + 4096) < unlock_mstats)
+ if ((_mstats + getpagesize()) < unlock_mstats)
log_error(INTERNAL_ERROR
"Maps lock %ld < unlock %ld",
(long)_mstats, (long)unlock_mstats);
next reply other threads:[~2011-03-06 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 16:47 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-12 18:29 LVM2 ./WHATS_NEW lib/mm/memlock.c agk
2011-06-12 0:23 agk
2011-03-30 13:06 zkabelac
2010-09-30 11:32 zkabelac
2010-06-24 8:29 zkabelac
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=20110306164744.13366.qmail@sourceware.org \
--to=mbroz@sourceware.org \
--cc=lvm-devel@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 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.