From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: "James G. Sack (jim)" <jsack@inostor.com>
Cc: linux-lvm@sistina.com, Mauelshagen@sistina.com
Subject: [linux-lvm] Re: Inconsistent LVM code in 2.4.23-rc1
Date: Wed Nov 19 05:09:02 2003 [thread overview]
Message-ID: <20031119120702.I28265@sistina.com> (raw)
In-Reply-To: <3FBA6614.357049F8@inostor.com>; from jsack@inostor.com on Tue, Nov 18, 2003 at 10:33:56AM -0800
On Tue, Nov 18, 2003 at 10:33:56AM -0800, James G. Sack (jim) wrote:
> [Hope this reaches the right place -- I'm not on any list -- please
> reply/cc direct]
>
> Linux kernel 2.4.23-rc1 has LVM patched code that differs from LVM 1.0.8
> (as well as cvs HEAD) from sistina.com
>
> Q: is the 2.4.23 code OK?
Yes, use the code in mainline.
> if yes, should it be in cvs
Yes.
Will check code differences and get back to Marcelo if necessary.
Regards,
Heinz -- The LVM Guy --
> if no, should somebody tell Marcelo?
>
>
>
> In essance, there are extra calls to vfree(snap_lv_ptr) at 4 places in
> lvm_do_vg_create() by virtue of a "goto copy_fault" --AND-- what looks
> like a correction to vg_ptr->pe_allocated
>
> A simple diff looks like
> ------------------------
> 1587,1588c1587
> < if (minor >= ABS_MAX_VG) {
> < kfree(vg_ptr);
> ---
> > if (minor >= ABS_MAX_VG)
> 1590d1588
> < }
> 1658c1656,1657
> < goto copy_fault;
> ---
> > lvm_do_vg_remove(minor);
> > return -EFAULT;
> 1669c1668,1669
> < goto copy_fault;
> ---
> > lvm_do_vg_remove(minor);
> > return -EFAULT;
> 1679c1679,1680
> < goto copy_fault;
> ---
> > lvm_do_vg_remove(minor);
> > return -EFAULT;
> 1682c1683,1684
> < goto copy_fault;
> ---
> > lvm_do_vg_remove(minor);
> > return -EFAULT;
> 1697,1700d1698
> < copy_fault:
> < lvm_do_vg_remove(minor);
> < vfree(snap_lv_ptr);
> < return -EFAULT;
> 2597c2595
> < vg_ptr->pe_allocated -= old_lv->lv_allocated_le;
> ---
> > vg_ptr->pe_allocated -= old_lv->lv_allocated_snapshot_le;
> 2598a2597
> > old_lv->lv_allocated_snapshot_le = new_lv->lv_allocated_le;
> ---------------------------------------------------------------------------
>
> Regards,
> ..jim
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2003-11-19 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 7:22 [linux-lvm] Inconsistent LVM code in 2.4.23-rc1 James G. Sack (jim)
2003-11-19 5:09 ` Heinz J . Mauelshagen [this message]
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=20031119120702.I28265@sistina.com \
--to=mauelshagen@sistina.com \
--cc=jsack@inostor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.