public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Todd M. Roy" <troy@holstein.com>
To: Andrea Arcangeli <andrea@suse.de>,
	"Heinz J. Mauelshagen" <Heinz.Mauelshagen@t-online.de>,
	linux-kernel@vger.kernel.org
Subject: lvm 0.9.1-beta1 still segfaults vgexport
Date: Sun, 14 Jan 2001 09:31:29 -0500	[thread overview]
Message-ID: <3A61B841.81B1D0F5@holstein.com> (raw)
In-Reply-To: <3A45192F.8C149F93@softhome.net> <20001227205336.A10446@athlon.random> <200101081918.f08JIrT06681@pcx4168.holstein.com> <20010108234339.F27646@athlon.random> <3A5B3422.F63D7DDD@holstein.com> <20010109170424.A29468@athlon.random> <3A5BBD0E.9F7DA88B@holstein.com> <20010110024743.R29904@athlon.random>

Andrea,
  Sorry to say but lvm 0.9.1-beta1 still segfaults
at the same place, line 140 of pv_read_all_pv_of_vg.c
pv_this is still null.
This with a straight 2.4.0 kernel with an onstream tape
patch and the generated lvm patch.  Lvm is a module (on
my home machine).
\x18\x13
-- todd --
gdb /sbin/vgexport core:
...

#0  0x400427f3 in pv_read_all_pv_of_vg (vg_name=0xbffff794 "vg01PV_EXP", 
    pv=0xbffff710, reread=0) at pv_read_all_pv_of_vg.c:140
140	      for ( p = 0; pv_this[p] != NULL; p++) {
(gdb) print pv_this
$1 = (pv_v2_t **) 0x0
(gdb) bt
#0  0x400427f3 in pv_read_all_pv_of_vg (vg_name=0xbffff794 "vg01PV_EXP", 
    pv=0xbffff710, reread=0) at pv_read_all_pv_of_vg.c:140
#1  0x400487af in vg_read (vg_name=0xbffff794 "vg01PV_EXP",
vg=0xbffff750)
    at vg_read.c:61
#2  0x4004733d in vg_check_exist (vg_name=0xbffff794 "vg01PV_EXP")
    at vg_check_exist.c:54
#3  0x80491ee in main (argc=2, argv=0xbffff8cc) at vgexport.c:182
#4  0x4007b213 in __libc_start_main (main=0x8048d00 <main>, argc=2, 
    ubp_av=0xbffff8cc, init=0x80489c4 <_init>, fini=0x80495b4 <_fini>, 
    rtld_fini=0x4000d660 <_dl_fini>, stack_end=0xbffff8c4)
    at ../sysdeps/generic/libc-start.c:129
...
**********************************************************************
This footnote confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**********************************************************************
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-14 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-23 21:29 lvm 0.8 to 0.9 conversion? Todd M. Roy
2000-12-27 19:53 ` Andrea Arcangeli
2001-01-08 19:17   ` Todd M. Roy
2001-01-08 19:18   ` Todd M. Roy
2001-01-08 22:43     ` Andrea Arcangeli
     [not found]       ` <3A5B3422.F63D7DDD@holstein.com>
     [not found]         ` <20010109170424.A29468@athlon.random>
     [not found]           ` <3A5BBD0E.9F7DA88B@holstein.com>
     [not found]             ` <20010110024743.R29904@athlon.random>
2001-01-14 14:31               ` Todd M. Roy [this message]
2001-01-14 16:32                 ` lvm 0.9.1-beta1 still segfaults vgexport Andrea Arcangeli
2001-01-15  4:16                   ` [lvm-devel] " Andrea Arcangeli
2001-01-15 11:23                     ` Todd M. Roy

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=3A61B841.81B1D0F5@holstein.com \
    --to=troy@holstein.com \
    --cc=Heinz.Mauelshagen@t-online.de \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.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: 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