linux-ext4 - Re: Segfaults--they're back!

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]

Message-Id: <1215648977.6978.7.camel@mingming-laptop>
Date:	Wed, 09 Jul 2008 17:16:17 -0700
From:	Mingming Cao <cmm@...ibm.com>
To:	Gary Hawco <ghawco@....net>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Theodore Tso <tytso@....edu>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: Segfaults--they're back!


在 2008-07-09三的 15:00 +0000，Gary Hawco写道：
> Segfaults have returned with snapshots compiled after 070908--0010hrs GMT.
> 
> That one worked fine.
> 
> The next one I tried (070908/0025hrs GMT) caused segfaults in both Gentoo &
> Slackware (a first for Slackware) when trying to untar
> linux-2.6.26-rc9.tar.bz2 tarball)
> 
> I then rolled back two snapshots to 070908/0012hrs GMT) and it segfaulted
> in both operating systems doing same untarring function.
> 
> So, apparently, since 0010snapshot
> (ext4-patch-queue-bfb23cf4cd345552c774142cb10ac1225caf35f5.tar.gz) works fine
> 
> and 0012snapshot
> (ext4-patch-queue-be66b0c5c3f4293176301c0ddcb8db95b0576cb4.tar.gz)
> segfaults, the 
> Add ext4-fix-mb_find_next_bit-return.patch must be the culprit.
> 

Thanks for reporting this, 
commit be66b0c5c3f4293176301c0ddcb8db95b0576cb4 added
ext4-fix-mb_find_next_bit-return.patch

I have dropped  this patch from patch queue, could you please check if
the segment fault goes away?


Mingming
> Thanks,
> Gary
> 
> P.S. The latest snapshot from today @ 0303hrs GMT segfaults as well.
> 

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