linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: tytso@mit.edu
Cc: Girish Shilamkar <Girish.Shilamkar@Sun.COM>,
	Ext4 <linux-ext4@vger.kernel.org>,
	adilger@Sun.COM
Subject: Re: e2fsprogs segfaults during make check
Date: Mon, 08 Feb 2010 09:57:57 -0600	[thread overview]
Message-ID: <4B703485.9070301@redhat.com> (raw)
In-Reply-To: <20100208121619.GF4494@thunk.org>

tytso@mit.edu wrote:
> On Mon, Feb 08, 2010 at 01:01:26PM +0530, Girish Shilamkar wrote:
>> Hello,
>>      I found a problem while creating e2fsprogs rpms. Few of the tests
>> fail with segfault during make check. The tests are d_loaddump, f_dup4,
>> f_imagic_fs and r_resize_inode. This failure is only seen on rhel5,
>> x86_64. 
>>       On further searching I found that this error can reproduced when
>> e2fsprogs is configured with shared elf libraries. For example,
>> configure --enable-elf-shlibs, make; make check 
>> And this problem is seen from 1.41.7 version onwards.
>>
>> Any ideas/comments ?
> 
> Well, I run "make check" all the time during the course of my
> development, so it must be something unique with RHEL5.

FWIW, it was make check segfaulting that led me to run valgrind
and find that array problem.

It's probably the flags that rpm builds with by default, doing
a better job at catching this sort of thing?

Girish Shilamkar wrote:

>> #3) Try downloading:
>> > 
>> >     http://master.kernel.org/~tytso/e2fsprogs_1.41.10-rc1.tar.gz
>> > 
>> > ... and see if you can see the problem there.
> The problem is not seen for this version. Any tentative dates for 1.41.10 release ?

I'm guessing the problem was fixed by the resize2fs array
indexing patch.

-Eric

      parent reply	other threads:[~2010-02-08 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  7:31 e2fsprogs segfaults during make check Girish Shilamkar
2010-02-08 12:16 ` tytso
2010-02-08 14:20   ` Girish Shilamkar
2010-02-08 14:28     ` tytso
2010-02-08 15:57   ` Eric Sandeen [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=4B703485.9070301@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Girish.Shilamkar@Sun.COM \
    --cc=adilger@Sun.COM \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).