From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Gary Hawco <ghawco@cox.net>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>, Mingming <cmm@us.ibm.com>
Subject: Re: Segfaults--they're back!
Date: Thu, 10 Jul 2008 10:51:50 +0530 [thread overview]
Message-ID: <20080710052150.GC6764@skywalker> (raw)
In-Reply-To: <3.0.6.32.20080709150004.01bd9858@pop.west.cox.net>
On Wed, Jul 09, 2008 at 03:00:04PM +0000, Gary Hawco wrote:
> 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.
Is your file system full when this happens ? Which user space call cause
the segfault ? An strace should be able to help you find that. We
actually have modified ext4 to give SIGBUS when we hit ENOSPC during
mmap write. For ex:
root:/ext4# /root/mmaptest ./test4 0 100
mmaping 0 to 100
Bus error (core dumped)
root:/ext4#
-aneesh
next prev parent reply other threads:[~2008-07-10 5:22 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
2008-07-10 5:21 ` Aneesh Kumar K.V [this message]
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=20080710052150.GC6764@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.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