public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW lib/activate/activate.c Date: Fri, 18 Feb 2011 14:26:00 -0000 [thread overview] Message-ID: <20110218142632.9030.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-02-18 14:26:31 Modified files: . : WHATS_NEW lib/activate : activate.c Log message: Remove fs_unlock after failed suspend Explicit fs_unlock() after failed suspend is not need - as it will happen automatically with nearest lv_info() or vg_unlock(). Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1916&r2=1.1917 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/activate/activate.c.diff?cvsroot=lvm2&r1=1.193&r2=1.194 --- LVM2/WHATS_NEW 2011/02/18 14:16:11 1.1916 +++ LVM2/WHATS_NEW 2011/02/18 14:26:31 1.1917 @@ -1,5 +1,6 @@ Version 2.02.85 - =================================== + Remove fs_unlock() from lv_suspend error path. Change memory locking semantic and use critical sections. Add configurable pv_min_size to select block devices by its size. Add function to read 64bit ints from config find_config_tree_int64. --- LVM2/lib/activate/activate.c 2011/02/18 14:16:11 1.193 +++ LVM2/lib/activate/activate.c 2011/02/18 14:26:31 1.194 @@ -1126,7 +1126,6 @@ if (!_lv_suspend_lv(lv, origin_only, lockfs, flush_required)) { critical_section_dec(cmd); - fs_unlock(); goto out; }
next reply other threads:[~2011-02-18 14:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-18 14:26 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-01-25 22:16 zkabelac 2010-08-16 23:29 agk 2010-07-12 11:37 prajnoha 2010-05-21 14:34 zkabelac 2010-01-27 13:24 mbroz 2009-12-03 19:23 mbroz 2009-12-01 19:10 mbroz 2009-10-30 13:07 agk 2009-09-29 18:50 agk 2009-09-29 15:17 mbroz 2007-08-01 20:29 jbrassow 2006-12-20 16:19 agk 2005-12-22 16:13 agk 2004-05-11 17:09 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=20110218142632.9030.qmail@sourceware.org \ --to=zkabelac@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).