From: Stefan Priebe - Profihost AG Subject: Re: Call trace in ext4_es_lru_add on 3.10 stable Date: Wed, 26 Nov 2014 09:06:43 +0100 Message-ID: <54758A13.20209@profihost.ag> References: <20140918192131.GD19520@thunk.org> <541B32A1.3080706@profihost.ag> <20140918194311.GE19520@thunk.org> <541FC817.7030401@profihost.ag> <20140922164715.GB4572@thunk.org> <54206AA2.1050607@profihost.ag> <20140922202004.GF4572@thunk.org> <54212641.9010808@profihost.ag> <20140923094204.GB2359@quack.suse.cz> <54216641.8090608@profihost.ag> <20140923144340.GI2359@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Theodore Ts'o , linux-ext4@vger.kernel.org, "p.herz@profihost.ag >> Philipp Herz - Profihost AG" , stable@vger.kernel.org, Zheng Liu To: Jan Kara Return-path: In-Reply-To: <20140923144340.GI2359@quack.suse.cz> Sender: stable-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Hi all, i'm still getting a lot of those call traces: " Call Trace: [] ext4_es_lru_add+0x26/0x80 [ext4] [] ext4_es_insert_extent+0x96/0x100 [ext4] [] ? ext4_find_delalloc_range+0x23/0x60 [ext4] [] ext4_map_blocks+0x111/0x450 [ext4] [] _ext4_get_block+0x87/0x190 [ext4] [] ext4_get_block+0x16/0x20 [ext4] [] generic_block_bmap+0x3f/0x50 [] ? jbd2_journal_file_buffer+0x4e/0x80 [jbd2] [] ? mapping_tagged+0x12/0x20 [] ext4_bmap+0x91/0xf0 [ext4] [] bmap+0x1e/0x30 [] jbd2_journal_bmap+0x33/0xb0 [jbd2] [] jbd2_journal_next_log_block+0x7d/0x90 [jbd2] [] jbd2_journal_commit_transaction+0x7f8/0x1ae0 [jbd2] [] ? idle_balance+0xd3/0x110 [] ? lock_timer_base.isra.35+0x38/0x70 [] kjournald2+0xba/0x230 [jbd2] [] ? finish_wait+0x80/0x80 [] ? jbd2_journal_release_jbd_inode+0x130/0x130 [jbd2] [] kthread+0xc0/0xd0 [] ? kthread_create_on_node+0x130/0x130 [] ret_from_fork+0x7c/0xb0 [] ? kthread_create_on_node+0x130/0x130 " Is there any chance to fix them in vanilla 3.10.61? Greets, Stefan