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 WHATS_NEW_DM Date: Thu, 19 Nov 2009 19:42:00 -0000 [thread overview] Message-ID: <20091119194258.326.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2009-11-19 19:42:57 Modified files: . : WHATS_NEW WHATS_NEW_DM Log message: . Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1318&r2=1.1319 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.316&r2=1.317 --- LVM2/WHATS_NEW 2009/11/19 19:00:34 1.1318 +++ LVM2/WHATS_NEW 2009/11/19 19:42:57 1.1319 @@ -1,18 +1,18 @@ Version 2.02.55 - 19th November 2009 ==================================== - Fix a possible deadlock in mirror code due to memlock refcount mismatch. - Enable dmeventd event handlers to properly scan devices. - Do not activate directly not visible volumes in vgchange. - Fix pvmove region_size oveflow for very large PVs. - Fix lvcreate and lvresize processing of %PVS argument. + Fix deadlock when changing mirrors due to unpaired memlock refcount changes. + Use separate memlock counter for dmeventd handlers to permit device scanning. + Directly restrict vgchange to activating visible LVs. + Fix pvmove region_size overflow for very large PVs. + Fix lvcreate and lvresize %PVS argument always to use sensible total size. Tidy some uses of arg_count and introduce arg_is_set. Export outnl and indent functions for modules. Flush stdout after yes/no prompt. Update vgsplit and vgcreate to use vg_set_clustered. - Add vg_mda_count and vg_set_clustered library function. + Add vg_mda_count and vg_set_clustered library functions. Add more vgcreate and vgsplit nightly tests. Insert some missing stack macros into activation code. - Recognise DRBD device part and handle it similar to MD devices. + Recognise DRBD devices and handle them like md devices. Version 2.02.54 - 26th October 2009 =================================== --- LVM2/WHATS_NEW_DM 2009/11/19 19:00:34 1.316 +++ LVM2/WHATS_NEW_DM 2009/11/19 19:42:57 1.317 @@ -2,7 +2,7 @@ ==================================== Fix install_device-mapper Makefile target to not build dmeventd plugins. Support udev flags even when udev_sync is disabled or not compiled in. - Remove 'last_rule' from udev rules: honor ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}. + Remove 'last_rule' from udev rules: honour DM_UDEV_DISABLE_OTHER_RULES_FLAG. Add dmsetup --inactive support. Add dm_task_query_inactive_table to libdevmapper for kernel driver >= 4.16. Fix hash lookup segfault when keys compared are different lengths.
next reply other threads:[~2009-11-19 19:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-19 19:42 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-04-29 19:05 agk 2010-07-27 21:57 agk 2010-01-15 16:18 jbrassow 2010-01-13 21:48 snitzer 2010-01-05 21:33 snitzer 2009-10-27 0:52 agk
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=20091119194258.326.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: linkBe 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).