public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/mm/memlock.c
Date: Sun, 12 Jun 2011 00:23:00 -0000 [thread overview]
Message-ID: <20110612002351.21003.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2011-06-12 00:23:50
Modified files:
. : WHATS_NEW
lib/mm : memlock.c
Log message:
Disable critical section internal errors until this can be fixed properly
in libdevmapper.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2011&r2=1.2012
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/mm/memlock.c.diff?cvsroot=lvm2&r1=1.43&r2=1.44
--- LVM2/WHATS_NEW 2011/06/11 00:03:06 1.2011
+++ LVM2/WHATS_NEW 2011/06/12 00:23:50 1.2012
@@ -1,5 +1,6 @@
Version 2.02.86 -
=================================
+ Downgrade critical_section errors to debug level until it is moved to libdm.
Fix ignored background polling default in vgchange -ay.
Fix pvmove activation sequences to avoid trapped I/O with multiple LVs.
Annotate critical section debug messages.
--- LVM2/lib/mm/memlock.c 2011/06/11 00:03:07 1.43
+++ LVM2/lib/mm/memlock.c 2011/06/12 00:23:50 1.44
@@ -405,8 +405,9 @@
void critical_section_dec(struct cmd_context *cmd, const char *reason)
{
+ /* FIXME Maintain accurate suspended device counter in libdevmapper */
if (!_critical_section_count)
- log_error(INTERNAL_ERROR "_critical_section has dropped below 0.");
+ log_debug("_critical_section has dropped below 0.");
--_critical_section_count;
log_debug("critical_section_dec to %d (%s).", _critical_section_count,
reason);
next reply other threads:[~2011-06-12 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 0:23 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-12 18:29 agk
2011-03-30 13:06 zkabelac
2011-03-06 16:47 mbroz
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=20110612002351.21003.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).