From: Tony Vroon <tony@linx.net>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Nick Bowler <nbowler@elliptictech.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: BUG in ext4 with 2.6.37-rc1
Date: Sat, 06 Nov 2010 01:06:50 +0000 [thread overview]
Message-ID: <1289005610.2961.21.camel@localhost> (raw)
In-Reply-To: <0C557864-9D5C-45A3-8DDF-114E4DD22258@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
On Fri, 2010-11-05 at 20:33 -0400, Theodore Tso wrote:
> And if you have the stack trace easily to hand, it would be useful to make sure that part is the same as well.
Seemingly identical between 2.6.36-09452-g2d10d87 &
2.6.37-rc1-00040-g0660a9b, both had cvs as the active process.
This one is from 2.6.37-rc1-00040-g0660a9b:
Call Trace:
[<ffffffff810e6716>] ? ext4_bio_write_page+0x176/0x30a
[<ffffffff810e25db>] ? mpage_da_submit_io+0x2ad/0x31e
[<ffffffff8106d034>] ? pagevec_lookup_tag+0x18/0x1f
[<ffffffff810e5c56>] ? write_cache_pages_da+0xad/0x36d
[<ffffffff810e5ac3>] ? mpage_da_map_and_submit+0x2c4/0x2da
[<ffffffff810edbba>] ? ext4_journal_start_sb+0xd4/0x108
[<ffffffff810269ac>] ? should_resched+0x5/0x26
[<ffffffff810a2f26>] ? _cond_resched+0x9/0x1e
[<ffffffff810e61ee>] ? ext4_da_writepages+0x2d8/0x422
[<ffffffff810b3471>] ? __getblk+0x1c/0x2d4
[<ffffffff81065cad>] ? __filemap_fdatawrite_range+0x48/0x4d
[<ffffffff810ff15c>] ? jbd2_journal_begin_ordered_truncated+0x72/0x9b
[<ffffffff810bb060>] ? fsnotify_clear_marks_by_inode+0x8a/0xc7
[<ffffffff810e5359>] ? ext4_evict_inode+0x56/0x241
[<ffffffff810a4c62>] ? evict+0x1a/0x89
[<ffffffff810a51dd>] ? iput+0x20d/0x246
[<ffffffff8109d85f>] ? do_unlinkat+0xf4/0x14c
[<ffffffff810029ab>] ? system_call_fastpath+0x16/0x1b
> Many thanks,
> -- Ted
Regards,
--
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-11-06 1:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 20:20 BUG in ext4 with 2.6.37-rc1 Nick Bowler
2010-11-03 18:14 ` [PATCH -BUGFIX] " Ted Ts'o
2010-11-03 18:22 ` Nick Bowler
2010-11-03 20:53 ` Nick Bowler
2010-11-07 21:21 ` Ted Ts'o
2010-11-07 22:53 ` Tony Vroon
2010-11-08 1:19 ` Dave Chinner
2010-11-08 5:00 ` [PATCH -v3] ext4: handle writeback of inodes which are being freed Ted Ts'o
2010-11-08 6:05 ` [PATCH -v4] " Ted Ts'o
2010-11-08 16:28 ` Nick Bowler
2010-11-08 16:54 ` Ted Ts'o
2010-11-08 6:43 ` [PATCH -v3] " Dave Chinner
2010-11-03 18:14 ` BUG in ext4 with 2.6.37-rc1 Eric Sandeen
2010-11-03 22:56 ` Dave Chinner
2010-11-05 23:09 ` Tony Vroon
2010-11-06 0:33 ` Theodore Tso
2010-11-06 0:39 ` Tony Vroon
2010-11-06 12:50 ` Ted Ts'o
2010-11-06 1:06 ` Tony Vroon [this message]
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=1289005610.2961.21.camel@localhost \
--to=tony@linx.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.