linux-ext4 - Re: e2fsprogs segfaults during make check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 08 Feb 2010 19:50:17 +0530
From:	Girish Shilamkar <Girish.Shilamkar@....COM>
To:	tytso@....edu
Cc:	Ext4 <linux-ext4@...r.kernel.org>, adilger@....COM
Subject: Re: e2fsprogs segfaults during make check

On Mon, 2010-02-08 at 07:16 -0500, tytso@....edu wrote:
> Well, I run "make check" all the time during the course of my
> development, so it must be something unique with RHEL5.
That is the surprising part, no other distros had problem. Even
rhel5/i686 passes all the tests.

> #1) Does it show up if you just unpack a source tree, and do a
>  "configure; make; make check" run in RHEL 5?
No, it doesn't show up. Problem appears when it is configured with 
--enable-elf-shlibs !!

> #2)  In the build directory, cd to tests, and then run the command:
> 
>    (. $(srcdir)/tests/test_config; debugfs)
> 
> .. and see if you get a core dump.  (Replace $(srcdir) with the top
> level source tree directory.  If you are building in the source tree,
> you can just do "(. test_config ; debugfs)"; if you are building with
> the build directory located in a "build" subdirectory under the source
> tree, you could do "(. ../tests/test_config ; debugfs)", etc.
> 
> If you do get a core dump, run it under gdb and get a stack trace,
> and/or see if anything is showing up in stderr that might be help
> explain what's going on.
Tried that before but there were no segfaults seen.

> #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 ?

Thanks,
Girish


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html