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/metadata/metadata-exporte ... Date: Fri, 28 Oct 2011 20:12:00 -0000 [thread overview] Message-ID: <20111028201256.26622.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-10-28 20:12:55 Modified files: . : WHATS_NEW lib/metadata : metadata-exported.h metadata.c Log message: Add last_seg Implement a function to return the last segment in a LV. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2173&r2=1.2174 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/metadata-exported.h.diff?cvsroot=lvm2&r1=1.216&r2=1.217 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/metadata.c.diff?cvsroot=lvm2&r1=1.470&r2=1.471 --- LVM2/WHATS_NEW 2011/10/28 20:06:49 1.2173 +++ LVM2/WHATS_NEW 2011/10/28 20:12:54 1.2174 @@ -1,5 +1,6 @@ Version 2.02.89 - ================================== + Add last_seg(lv) internal function. Support empty string for log/prefix. Fix regression that allowed mirrored logs for cluster mirrors. Don't print char type[8] as a plain string in pvck PV type. --- LVM2/lib/metadata/metadata-exported.h 2011/10/21 11:38:35 1.216 +++ LVM2/lib/metadata/metadata-exported.h 2011/10/28 20:12:55 1.217 @@ -660,6 +660,7 @@ const char *pvid); /* Find LV segment containing given LE */ struct lv_segment *first_seg(const struct logical_volume *lv); +struct lv_segment *last_seg(const struct logical_volume *lv); /* --- LVM2/lib/metadata/metadata.c 2011/10/24 10:24:40 1.470 +++ LVM2/lib/metadata/metadata.c 2011/10/28 20:12:55 1.471 @@ -1906,6 +1906,16 @@ return NULL; } +struct lv_segment *last_seg(const struct logical_volume *lv) +{ + struct lv_segment *seg; + + dm_list_iterate_back_items(seg, &lv->segments) + return seg; + + return NULL; +} + int vg_remove_mdas(struct volume_group *vg) { struct metadata_area *mda;
next reply other threads:[~2011-10-28 20:12 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-28 20:12 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-12-01 0:09 jbrassow 2011-10-07 14:56 jbrassow 2011-09-14 9:57 zkabelac 2011-09-07 8:34 zkabelac 2011-08-18 19:43 jbrassow 2011-08-18 19:34 jbrassow 2011-03-11 14:56 prajnoha 2011-03-02 20:00 mbroz 2011-02-25 14:02 prajnoha 2010-05-21 14:07 zkabelac 2010-05-21 12:55 zkabelac 2010-05-21 12:52 zkabelac 2010-05-14 15:19 jbrassow 2010-03-16 15:30 agk 2010-03-16 14:37 agk 2009-07-14 2:19 wysochanski 2009-06-05 20:00 mbroz 2009-06-01 14:43 mbroz 2009-02-03 16:19 wysochanski 2008-04-23 14:33 wysochanski 2008-02-13 20:01 meyering 2008-01-18 22:02 agk 2008-01-16 18:15 agk 2008-01-07 20:42 mbroz 2007-11-15 2:20 agk 2007-10-12 14:08 wysochanski 2007-09-20 21:39 wysochanski 2007-08-30 20:30 wysochanski 2007-08-21 17:38 wysochanski 2007-07-23 17:27 wysochanski
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=20111028201256.26622.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).