From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758216Ab3ANS4Q (ORCPT ); Mon, 14 Jan 2013 13:56:16 -0500 Received: from merlin.infradead.org ([205.233.59.134]:50397 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758200Ab3ANS4O (ORCPT ); Mon, 14 Jan 2013 13:56:14 -0500 Message-ID: <50F454C2.6000509@kernel.dk> Date: Mon, 14 Jan 2013 19:56:02 +0100 From: Jens Axboe MIME-Version: 1.0 To: sedat.dilek@gmail.com CC: linux-next , linux-fsdevel , LKML , Stephen Rothwell , linux-mm , Andrew Morton , Al Viro Subject: Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2013-01-14 19:33, Sedat Dilek wrote: > Hi, > > while running LTP lite on my next-20130114 kernel I hit this > call-trace (file attached). > > Looks to me like problem in the block layer, but not sure. > Might one of the experts have look at it? Really? 600kb of data to look through? Can't you just paste the actual error, I can't even find it... -- Jens Axboe