From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
"p.herz@profihost.ag >> Philipp Herz - Profihost AG"
<p.herz@profihost.ag>,
stable@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: Call trace in ext4_es_lru_add on 3.10 stable
Date: Wed, 26 Nov 2014 09:06:43 +0100 [thread overview]
Message-ID: <54758A13.20209@profihost.ag> (raw)
In-Reply-To: <20140923144340.GI2359@quack.suse.cz>
Hi all,
i'm still getting a lot of those call traces:
"
Call Trace:
[<ffffffffa01d7006>] ext4_es_lru_add+0x26/0x80 [ext4]
[<ffffffffa01d7286>] ext4_es_insert_extent+0x96/0x100 [ext4]
[<ffffffffa01c3fd3>] ? ext4_find_delalloc_range+0x23/0x60 [ext4]
[<ffffffffa019b781>] ext4_map_blocks+0x111/0x450 [ext4]
[<ffffffffa019d167>] _ext4_get_block+0x87/0x190 [ext4]
[<ffffffffa019d2c6>] ext4_get_block+0x16/0x20 [ext4]
[<ffffffff8117f73f>] generic_block_bmap+0x3f/0x50
[<ffffffffa013f4ae>] ? jbd2_journal_file_buffer+0x4e/0x80 [jbd2]
[<ffffffff810f6242>] ? mapping_tagged+0x12/0x20
[<ffffffffa019ad71>] ext4_bmap+0x91/0xf0 [ext4]
[<ffffffff811686de>] bmap+0x1e/0x30
[<ffffffffa0148063>] jbd2_journal_bmap+0x33/0xb0 [jbd2]
[<ffffffffa014831d>] jbd2_journal_next_log_block+0x7d/0x90 [jbd2]
[<ffffffffa0140238>] jbd2_journal_commit_transaction+0x7f8/0x1ae0 [jbd2]
[<ffffffff81084e13>] ? idle_balance+0xd3/0x110
[<ffffffff8105a018>] ? lock_timer_base.isra.35+0x38/0x70
[<ffffffffa014593a>] kjournald2+0xba/0x230 [jbd2]
[<ffffffff81070360>] ? finish_wait+0x80/0x80
[<ffffffffa0145880>] ? jbd2_journal_release_jbd_inode+0x130/0x130 [jbd2]
[<ffffffff8106fb60>] kthread+0xc0/0xd0
[<ffffffff8106faa0>] ? kthread_create_on_node+0x130/0x130
[<ffffffff81554c2c>] ret_from_fork+0x7c/0xb0
[<ffffffff8106faa0>] ? kthread_create_on_node+0x130/0x130
"
Is there any chance to fix them in vanilla 3.10.61?
Greets,
Stefan
next prev parent reply other threads:[~2014-11-26 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:08 Call trace in ext4_es_lru_add on 3.10 stable Stefan Priebe - Profihost AG
2014-09-18 19:21 ` Theodore Ts'o
2014-09-18 19:29 ` Stefan Priebe
2014-09-18 19:43 ` Theodore Ts'o
2014-09-22 6:56 ` Stefan Priebe
2014-09-22 16:47 ` Theodore Ts'o
2014-09-22 18:29 ` Stefan Priebe
2014-09-22 20:20 ` Theodore Ts'o
2014-09-23 7:50 ` Stefan Priebe - Profihost AG
2014-09-23 9:42 ` Jan Kara
2014-09-23 12:23 ` Stefan Priebe
2014-09-23 14:43 ` Jan Kara
2014-11-26 8:06 ` Stefan Priebe - Profihost AG [this message]
2014-11-26 8:25 ` Jan Kara
2014-11-26 10:28 ` Stefan Priebe - Profihost AG
2014-11-26 10:38 ` Jan Kara
2014-11-26 15:11 ` Stefan Priebe - Profihost AG
2014-11-26 20:26 ` Jan Kara
2014-11-26 20:33 ` Stefan Priebe
2014-12-04 15:06 ` Stefan Priebe - Profihost AG
2014-12-04 18:35 ` Jan Kara
2014-12-15 9:48 ` Stefan Priebe - Profihost AG
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=54758A13.20209@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=p.herz@profihost.ag \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.com \
/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.