From: Theodore Tso <tytso@mit.edu>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14256] kernel BUG at fs/ext3/super.c:435
Date: Fri, 9 Oct 2009 21:31:31 -0400 [thread overview]
Message-ID: <20091010013131.GC18440@mit.edu> (raw)
In-Reply-To: <200910092201.n99M1iBY007169@demeter.kernel.org>
On Fri, Oct 09, 2009 at 10:01:44PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> > Not fixed in 2.6.32-rc3. A glibc rebuild + install triggered the
> > exact same bug on the third machine.
Can you isolate this down to something simpler? Will "make install"
followed by a reboot be sufficient to replicate the assertion failure?
If it does, will copying in a new version of libc.so.6 and then
rebooting be enough to trigger the assert failure?
Thanks,
- Ted
next prev parent reply other threads:[~2009-10-10 1:32 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 21:48 [Bug 14256] New: kernel BUG at fs/ext3/super.c:435 bugzilla-daemon
2009-10-04 20:47 ` [Bug 14256] " bugzilla-daemon
2009-10-09 22:01 ` bugzilla-daemon
2009-10-10 1:31 ` Theodore Tso [this message]
2009-10-12 13:48 ` Mikael Pettersson
2009-10-10 1:31 ` bugzilla-daemon
2009-10-12 13:48 ` bugzilla-daemon
2009-10-12 16:19 ` bugzilla-daemon
2009-11-05 16:07 ` bugzilla-daemon
2009-11-05 16:13 ` bugzilla-daemon
2009-11-11 15:27 ` bugzilla-daemon
2009-11-11 15:29 ` bugzilla-daemon
2009-11-20 15:11 ` bugzilla-daemon
2009-11-21 14:27 ` bugzilla-daemon
2009-12-08 11:12 ` bugzilla-daemon
2009-12-08 11:47 ` bugzilla-daemon
2009-12-14 12:40 ` bugzilla-daemon
2009-12-14 14:46 ` bugzilla-daemon
2009-12-15 9:08 ` bugzilla-daemon
2009-12-29 13:18 ` bugzilla-daemon
2010-01-11 21:59 ` bugzilla-daemon
2010-01-11 22:55 ` bugzilla-daemon
2010-01-12 16:03 ` bugzilla-daemon
2010-01-12 17:30 ` bugzilla-daemon
2010-01-12 20:12 ` bugzilla-daemon
2010-01-12 23:25 ` bugzilla-daemon
2010-01-13 0:34 ` bugzilla-daemon
2010-01-18 22:41 ` bugzilla-daemon
2010-01-19 19:56 ` bugzilla-daemon
2010-01-19 19:57 ` bugzilla-daemon
2010-01-19 23:24 ` bugzilla-daemon
2010-01-20 10:40 ` bugzilla-daemon
2010-01-20 13:52 ` bugzilla-daemon
2010-01-20 18:11 ` bugzilla-daemon
2010-01-20 19:10 ` bugzilla-daemon
2010-01-20 19:29 ` bugzilla-daemon
2010-01-20 19:54 ` bugzilla-daemon
2010-01-20 20:09 ` bugzilla-daemon
2010-01-23 22:18 ` bugzilla-daemon
2010-01-24 11:28 ` bugzilla-daemon
2010-01-24 17:13 ` bugzilla-daemon
2010-01-24 18:17 ` bugzilla-daemon
2010-01-24 18:20 ` bugzilla-daemon
2010-01-24 19:27 ` bugzilla-daemon
2010-01-25 1:37 ` bugzilla-daemon
2010-01-25 10:29 ` bugzilla-daemon
2010-01-25 12:07 ` bugzilla-daemon
2010-01-28 17:19 ` bugzilla-daemon
2010-01-28 17:23 ` bugzilla-daemon
2010-01-28 17:24 ` bugzilla-daemon
2010-01-28 17:25 ` bugzilla-daemon
2010-01-28 17:55 ` bugzilla-daemon
2010-02-10 19:16 ` bugzilla-daemon
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=20091010013131.GC18440@mit.edu \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).