From: Jan Niehusmann <list064@gondor.com>
To: linux-lvm@sistina.com
Cc: lvm-devel@sistina.com, Rik van Riel <riel@conectiva.com.br>
Subject: Re: [lvm-devel] Re: [linux-lvm] LVM 0.9 vgscan problem
Date: Fri, 5 Jan 2001 12:38:20 +0100 [thread overview]
Message-ID: <20010105123820.A1886@gondor.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101041959040.1295-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Jan 04, 2001 at 08:01:10PM -0200
On Thu, Jan 04, 2001 at 08:01:10PM -0200, Rik van Riel wrote:
> But when I type (with the IOP10 tools) the following
> all hell breaks loose:
>
> # vgextend vg0 /dev/hda5 (the previously removed PV)
>
> The oops is below.
This is already known, a fix is in cvs. (But I didn't try it, I just remembered
that somebody mentioned it on the mailinglist).
I think the following patch will do the job:
Index: lvm.c
===================================================================
RCS file: /data/cvs/LVM/kernel/lvm.c,v
retrieving revision 1.7.2.1
retrieving revision 1.7.2.2
diff -u -1 -b -p -r1.7.2.1 -r1.7.2.2
--- lvm.c 2000/11/26 12:21:37 1.7.2.1
+++ lvm.c 2000/11/27 23:48:01 1.7.2.2
@@ -143,2 +143,3 @@
* 26/11/2000 - corrected #ifdef locations for PROC_FS
+ * 28/11/2000 - fixed lvm_do_vg_extend() NULL pointer BUG
*
@@ -2089,4 +2090,5 @@ static int lvm_do_vg_extend(vg_t *vg_ptr
ret = lvm_do_pv_create(arg, vg_ptr, p);
- lvm_do_create_proc_entry_of_pv ( vg_ptr, pv_ptr);
if ( ret != 0) return ret;
+ pv_ptr = vg_ptr->pv[p];
+ lvm_do_create_proc_entry_of_pv ( vg_ptr, pv_ptr);
next prev parent reply other threads:[~2001-01-05 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 22:56 [linux-lvm] LVM 0.9 vgscan problem Rik van Riel
2001-01-04 17:49 ` Rik van Riel
2001-01-04 22:01 ` [lvm-devel] " Rik van Riel
2001-01-05 11:38 ` Jan Niehusmann [this message]
2001-01-05 11:57 ` Rik van Riel
2001-01-05 15:34 ` Heinz J. Mauelshagen
2001-01-05 15:10 ` Rik van Riel
2001-01-05 15:22 ` Chris Mason
2001-01-05 3:56 ` Paul Jakma
2001-01-05 15:29 ` Heinz J. Mauelshagen
2001-01-05 15:27 ` Paul Jakma
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=20010105123820.A1886@gondor.com \
--to=list064@gondor.com \
--cc=linux-lvm@sistina.com \
--cc=lvm-devel@sistina.com \
--cc=riel@conectiva.com.br \
/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