From: "James G. Sack (jim)" <jsack@inostor.com>
To: linux-lvm@sistina.com, Mauelshagen@Sistina.com
Subject: [linux-lvm] Inconsistent LVM code in 2.4.23-rc1
Date: Wed Nov 19 07:22:15 2003 [thread overview]
Message-ID: <3FBA6614.357049F8@inostor.com> (raw)
[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?
if yes, should it be in cvs
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
next reply other threads:[~2003-11-19 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 7:22 James G. Sack (jim) [this message]
2003-11-19 5:09 ` [linux-lvm] Re: Inconsistent LVM code in 2.4.23-rc1 Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 7:20 [linux-lvm] " Xose Vazquez Perez
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=3FBA6614.357049F8@inostor.com \
--to=jsack@inostor.com \
--cc=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 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.