From: Mingming Cao <cmm@us.ibm.com>
To: Gary Hawco <ghawco@cox.net>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: Segfaults--they're back!
Date: Wed, 09 Jul 2008 17:16:17 -0700 [thread overview]
Message-ID: <1215648977.6978.7.camel@mingming-laptop> (raw)
In-Reply-To: <3.0.6.32.20080709150004.01bd9858@pop.west.cox.net>
在 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-10 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 15:00 Segfaults--they're back! Gary Hawco
2008-07-10 0:16 ` Mingming Cao [this message]
2008-07-10 5:21 ` Aneesh Kumar K.V
2008-07-10 11:02 ` Theodore Tso
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=1215648977.6978.7.camel@mingming-laptop \
--to=cmm@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ghawco@cox.net \
--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