All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Lixfeld" <jlixfeld@andromedas.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots
Date: Thu, 4 Oct 2001 10:01:09 -0400	[thread overview]
Message-ID: <009701c14cdd$06877ab0$836788cf@industry> (raw)
In-Reply-To: <009601c14cc9$27e34db0$836788cf@industry>

Since I'm having trouble with rc-4 can I use another version that is
still compatible with everything and won't segfault!? :)

> -----Original Message-----
> From: linux-lvm-admin@sistina.com 
> [mailto:linux-lvm-admin@sistina.com] On Behalf Of Jason A. Lixfeld
> Sent: October 4, 2001 7:39 AM
> To: linux-lvm@sistina.com
> Subject: RE: [linux-lvm] lvcreate segfault in 
> vg_setup_pointers_for_snapshots
> 
> 
> 
> 
> Ok, done...
> 
> http://www.andromedas.com/lvm/session.log
> 
> It's 35MB and I'm only on a 3MB DSL connection so it's gonna 
> take a while to load! :)
> 
> > -----Original Message-----
> > From: linux-lvm-admin@sistina.com
> > [mailto:linux-lvm-admin@sistina.com] On Behalf Of Andreas Dilger
> > Sent: October 4, 2001 2:05 AM
> > To: linux-lvm@sistina.com
> > Subject: Re: [linux-lvm] lvcreate segfault in 
> > vg_setup_pointers_for_snapshots
> > 
> > 
> > 
> > On Oct 03, 2001  23:46 -0400, Jason A. Lixfeld wrote:
> > > Wow!  Lots and LOTS of stuff!!  Didn't think it was ever going to
> > > end!!
> > 
> > Some of it is even useful.  Maybe you can include some of the
> > stuff at the end, or put it on a web page somewhere.
> > 
> > > Here's what yer looking for:
> > > 
> > > #0  lv_create (vg=0x8, lv=0xbffffb74, 
> > >     lv_name=0xbffffb98
> > > 
> > 
> "????????????????????????????????\002???!???,???<???D???T???b???s???\2
> > > 01
> > > ???\214???\227???????")
> > >     at lv_create_remove.c:42
> > > #1  0x0804b03d in strcpy () at ../sysdeps/generic/strcpy.c:31
> > 
> > So it is dereferencing an uninitialized string (or so it
> > appears).  It may be that the string is corrupted elsewhere, 
> > however.  I'm surprised that
> > lv_check_name() in lv_create_remove() didn't catch this.  
> > However, this may also be a red herring, since sometimes GDB 
> > shows junk.
> > 
> > It is also suspicious because the lv and lv_name pointers are
> > 0x24 apart, which shouldn't be the case since lv_name is the 
> > first item in lv_t.
> > 
> > > #2  0x4006c177 in __libc_start_main (main=0x8049390 <strcpy+384>,
> > > argc=8, ubp_av=0xbffffb74, init=0x8048e88 <_init>,
> > >     fini=0x804b4d0 <_fini>, rtld_fini=0x4000e184 <_dl_fini>,
> > > stack_end=0xbffffb6c) at ../sysdeps/generic/libc-start.c:129
> > 
> > If you try running with "export MALLOC_CHECK_=2 gdb
> > <path>/lvcreate", it may give more indication as to where the 
> > actual corruption is happening.
> > 
> > I just recompiled the tools, and did not have any problems
> > with lvcreate, so it must be something strange.
> > 
> > Cheers, Andreas
> > --
> > Andreas Dilger  \ "If a man ate a pound of pasta and a pound
> > of antipasto,
> >                  \  would they cancel out, leaving him 
> still hungry?"
> > http://www-mddsp.enel.ucalgary.ca/People/adilger/             
> >   -- Dogbert
> > 
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linu> x-lvm
> > read the 
> > LVM HOW-TO at 
> > http://www.sistina.com/lvm/Pages/howto.html
> > 
> 
> 
> _______________________________________________
> 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
> 

  reply	other threads:[~2001-10-04 14:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 15:30 [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Paul Jakma
2001-10-03 18:22 ` Paul Jakma
2001-10-03 19:00   ` Paul Jakma
2001-10-03 19:12     ` svetljo
2001-10-03 19:30       ` Andreas Dilger
2001-10-03 19:40         ` svetljo
2001-10-03 19:52           ` Paul Jakma
2001-10-03 20:44             ` svetljo
2001-10-03 19:56         ` Paul Jakma
2001-10-04  0:45         ` Paul Jakma
2001-10-04  2:54           ` [linux-lvm] What have I done!? Jason A. Lixfeld
2001-10-04  3:06             ` Jason A. Lixfeld
2001-10-04  5:44             ` idsfa
2001-10-04 11:00               ` Jason A. Lixfeld
2001-10-04 11:24                 ` Jason A. Lixfeld
2001-10-04 17:33                   ` Andreas Dilger
2001-10-04 17:57                     ` Steven Lembark
2001-10-05  7:05                       ` Heinz J . Mauelshagen
2001-10-04  3:28           ` [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Jason A. Lixfeld
2001-10-04  3:33             ` Andreas Dilger
2001-10-04  3:46               ` Jason A. Lixfeld
2001-10-04  6:04                 ` Andreas Dilger
2001-10-04  7:05                   ` Sean Burford
2001-10-04 10:31                   ` Paul Jakma
2001-10-04 11:05                     ` Joe Thornber
2001-10-04 14:51                       ` Paul Jakma
2001-10-04 11:38                   ` Jason A. Lixfeld
2001-10-04 14:01                     ` Jason A. Lixfeld [this message]
2001-10-04 14:23                       ` Jason A. Lixfeld
2001-10-04 15:57                         ` Jason A. Lixfeld
2001-10-04 20:12                           ` Goetz Bock

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='009701c14cdd$06877ab0$836788cf@industry' \
    --to=jlixfeld@andromedas.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.