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 VERSION VERSION_DM WHATS_NEW WHATS_NEW_DM Date: Tue, 21 Dec 2010 01:08:00 -0000 [thread overview] Message-ID: <20101221010830.17827.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2010-12-21 01:08:30 Modified files: . : VERSION VERSION_DM WHATS_NEW WHATS_NEW_DM Log message: pre-release Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION.diff?cvsroot=lvm2&r1=1.264&r2=1.265 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION_DM.diff?cvsroot=lvm2&r1=1.73&r2=1.74 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1848&r2=1.1849 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.432&r2=1.433 --- LVM2/VERSION 2010/12/06 22:13:10 1.264 +++ LVM2/VERSION 2010/12/21 01:08:29 1.265 @@ -1 +1 @@ -2.02.79(2)-cvs (2010-12-06) +2.02.79(2)-cvs (2010-12-20) --- LVM2/VERSION_DM 2010/12/06 22:13:10 1.73 +++ LVM2/VERSION_DM 2010/12/21 01:08:29 1.74 @@ -1 +1 @@ -1.02.60-cvs (2010-12-06) +1.02.60-cvs (2010-12-20) --- LVM2/WHATS_NEW 2010/12/20 14:38:22 1.1848 +++ LVM2/WHATS_NEW 2010/12/21 01:08:29 1.1849 @@ -1,16 +1,18 @@ -Version 2.02.79 - -=================================== +Version 2.02.79 - 20th December 2010 +==================================== + Remove some unused variables. Add missing test for reallocation error in _find_parallel_space(). - Add check for unlink error result in remove_lockfile() (dmeventd). - Use dm_free for dm_malloc-ed areas in _clog_ctr/_clog_dtr (cmirrord). Add checks for allocation errors in config node clonning. Fix error path if regex engine cannot be created in _build_matcher(). - Use char* arithmetic in target_version(), _process_all(), _targets(). + Use char* arithmetic in target_version(), _process_all() & _targets(). Fixing const cast gcc warnings in the code. Check read() and close() results in _get_cmdline(). Add const for struct config_node usage. Fix NULL pointer check in error path in clvmd do_command(). (2.02.78) Fix device.c #include to ensure 64-bit fopen64 use. (2.02.51) + Add copy_percent and snap_percent to liblvm. + Enhance vg_validate to ensure integrity of LV and PV structs referenced. + Enhance vg_validate to check composition of pvmove LVs. Create /var/run/lvm directory during clvmd initialisation if missing. Use new dm_prepare_selinux_context instead of dm_set_selinux_context. Avoid revalidating the label cache immediately after scanning. @@ -18,7 +20,7 @@ Don't skip full scan when independent mdas are present even if memlock is set. Set cmd->independent_metadata_areas if metadata/dirs or disk_areas in use. Cope better with an undefined target_percent operation in _percent_run. - Fix write to released memory in vg_release and rename to free_vg. (2.02.78) + Avoid writing to freed memory in vg_release and rename to free_vg. (2.02.78) Version 2.02.78 - 6th December 2010 =================================== --- LVM2/WHATS_NEW_DM 2010/12/20 13:23:11 1.432 +++ LVM2/WHATS_NEW_DM 2010/12/21 01:08:29 1.433 @@ -1,5 +1,8 @@ -Version 1.02.60 - -=================================== +Version 1.02.60 - 20th December 2010 +==================================== + Check for unlink failure in remove_lockfile() in dmeventd. + Use dm_free for dm_malloc-ed areas in _clog_ctr/_clog_dtr in cmirrord. + Use char* arithmetic in _process_all() & _targets() in dmsetup. Change dm_regex_create() API to accept const char * const *patterns. Add new dm_prepare_selinux_context fn to libdevmapper and use it throughout. Detect existence of new SELinux selabel interface during configure.
next reply other threads:[~2010-12-21 1:08 UTC|newest] Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-21 1:08 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-06 4:47 agk 2012-03-03 2:08 agk 2012-03-03 1:00 agk 2012-02-23 18:22 agk 2012-01-27 1:23 agk 2011-08-19 19:42 agk 2011-08-19 16:31 agk 2011-08-12 2:34 agk 2011-08-12 1:34 agk 2011-07-08 19:57 agk 2011-07-08 19:19 agk 2011-04-29 17:05 agk 2011-04-29 16:12 agk 2011-02-09 12:11 agk 2011-02-09 12:04 agk 2011-02-04 22:46 agk 2011-01-10 14:51 agk 2010-12-06 22:13 agk 2010-11-22 18:38 agk 2010-11-22 14:26 agk 2010-09-24 16:25 agk 2010-08-19 22:33 agk 2010-08-18 20:57 agk 2010-07-28 21:58 agk 2010-07-28 11:49 agk 2010-07-27 22:52 agk 2010-07-06 16:49 agk 2010-06-30 14:50 agk 2010-06-23 19:35 agk 2010-06-23 17:48 agk 2010-06-07 10:25 agk 2010-06-04 17:23 agk 2010-05-20 23:21 agk 2010-05-20 22:27 agk 2010-05-17 20:18 agk 2010-04-30 15:48 agk 2010-04-14 21:47 agk 2010-04-14 17:50 agk 2010-03-09 14:01 agk 2010-03-09 13:13 agk 2010-01-23 2:14 agk 2010-01-22 1:09 agk 2010-01-21 23:55 agk 2010-01-14 14:42 agk 2010-01-14 14:02 agk 2010-01-12 14:47 agk 2010-01-12 14:39 agk 2009-11-24 19:04 agk 2009-11-24 18:26 agk 2009-11-19 19:53 agk 2009-11-19 19:00 agk 2009-10-27 1:13 agk 2009-10-26 21:56 agk 2009-09-26 0:42 agk 2009-09-25 18:32 agk 2009-09-15 13:54 agk 2009-09-15 10:57 agk 2009-08-06 19:32 agk 2009-07-28 20:47 agk 2009-07-15 15:38 agk 2009-07-15 13:20 agk 2009-07-01 9:31 agk 2009-06-30 18:41 agk 2009-06-26 10:57 agk 2009-05-22 15:23 agk 2009-03-03 18:25 agk 2009-03-03 13:03 agk 2009-01-26 14:46 agk 2009-01-26 13:14 agk 2008-11-19 14:14 agk 2008-11-10 12:39 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=20101221010830.17827.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).