From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Patch for vg_status_with_pv_and_lv.c
Date: Mon May 6 08:33:05 2002 [thread overview]
Message-ID: <20020506153359.E26606@sistina.com> (raw)
In-Reply-To: <2D0AFEFEE711D611923E009027D39F2B02F140@cdserv.meridian-data.com>; from dstephenson@snapserver.com on Wed, May 01, 2002 at 12:22:13PM -0700
Dale,
thanks for the patch.
Soon to be in CVS...
Regards,
Heinz -- The LVM Guy --
On Wed, May 01, 2002 at 12:22:13PM -0700, Stephenson, Dale wrote:
> I'm not sure if I sent this patch out when I generated it (I'm guessing not,
> since it doesn't seem to be different in CVS), so I'm sending it out now.
>
> This patch solves a segfault in lvscan. When there was a problem reading
> the lv_list (lv_status_all_lv_of_vg() returned an error) in
> vg_status_with_pv_and_lv.c, the routine would still call
> vg_setup_pointers_for_snapshots. Since the error had prevented setting up
> the vg->lv[] array, this didn't work. I just moved
> vg_setup_pointers_for_snapshot inside the no error case. No one uses the vg
> if an error is returned, so it doesn't matter that it isn't setup for
> snapshots :->.
>
> Dale J. Stephenson
> steph@snapserver.com
>
> --- 1.0.3/tools/lib/vg_status_with_pv_and_lv.c.orig Thu Apr 11 10:45:18
> 2002
> +++ 1.0.3/tools/lib/vg_status_with_pv_and_lv.c Thu Apr 11 10:45:41 2002
> @@ -57,10 +57,10 @@
> for ( p = 0; pv[p] != NULL; p++) (*vg)->pv[p] = pv[p];
> for ( ; p < (*vg)->pv_max; p++) (*vg)->pv[p] = NULL;
> for ( l = 0; l < (*vg)->lv_max; l++) (*vg)->lv[l] = lv[l];
> - }
>
> - /* Set up core pointers for snapshots */
> - vg_setup_pointers_for_snapshots ( *vg);
> + /* Set up core pointers for snapshots */
> + vg_setup_pointers_for_snapshots ( *vg);
> + }
>
> debug_leave ( "vg_status_with_pv_and_lv -- LEAVING with ret: %d\n",
> ret);
> return ret;
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-05-06 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 14:16 [linux-lvm] Patch for vg_status_with_pv_and_lv.c Stephenson, Dale
2002-05-06 8:33 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 12:56 Dale J. Stephenson
2003-03-04 5:53 ` Heinz J . Mauelshagen
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=20020506153359.E26606@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.com \
/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