xfs
[Top] [All Lists]

Re: Hang in XFS reclaim on 3.7.0-rc3

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: Hang in XFS reclaim on 3.7.0-rc3
From: Torsten Kaiser <just.for.lkml@xxxxxxxxxxxxxx>
Date: Mon, 19 Nov 2012 07:50:06 +0100
Cc: xfs@xxxxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3Yh7xYaxRQAQIryQxi40QLE5MVxhih1Wq71BfgEm4Fc=; b=sECRQTqSfNukthVzKq3GioHzQslnaZr5kYNKyQ64yd7NNo5r1HGq5ZmW1qm+/IcBPv P9g5dOsbs4+h+v5MYm9UMfZiA50HyOU/ZsM7GUH7F4pmEGt97hwCE5U7JRNzBDoVWuFF hv5r5wkuBIRA2TWlQFH1ScGSna2Zr7wubf7EHJR7IVcV0doJVZcZ5jmnSuUFy9s5QI5D mzVdqWBWoN3GtPys+YytOKF9iVw6X1LfDthsGHW7/EGPla/yMUjm4QER3ia3TvDmelwA uzeotrc7EGoIBU0c+sTPXtSK4XDwdae7WjyhDiOKiojFndLOmhzDuldQn85cz7DQwelP 3CLQ==
In-reply-to: <20121118235105.GT14281@dastard>
References: <CAPVoSvSM9=hictqwT2rzZA-fU_XSwd-_FRzW_J+HQYj7iohTWQ@xxxxxxxxxxxxxx> <20121029222613.GU29378@dastard> <CAPVoSvQATjAVu-D477mrr6K9d0FeY7sH27cH-zNBYMJcRoUY0Q@xxxxxxxxxxxxxx> <CAPVoSvRks32ZM7n6U8but-vEj622TEFqAFdxXqS_6mRxyv=0Ew@xxxxxxxxxxxxxx> <CAPVoSvSKn2FuBhMF+3U1ueuEzBqL4CFTYFGXqGczTa42PgMjRw@xxxxxxxxxxxxxx> <20121118235105.GT14281@dastard>
On Mon, Nov 19, 2012 at 12:51 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> On Sun, Nov 18, 2012 at 04:29:22PM +0100, Torsten Kaiser wrote:
>> On Sun, Nov 18, 2012 at 11:24 AM, Torsten Kaiser
>> <just.for.lkml@xxxxxxxxxxxxxx> wrote:
>> > On Tue, Oct 30, 2012 at 9:37 PM, Torsten Kaiser
>> > <just.for.lkml@xxxxxxxxxxxxxx> wrote:
>> >> I will keep LOCKDEP enabled on that system, and if there really is
>> >> another splat, I will report back here. But I rather doubt that this
>> >> will be needed.
>> >
>> > After the patch, I did not see this problem again, but today I found
>> > another LOCKDEP report that also looks XFS related.
>> > I found it twice in the logs, and as both were slightly different, I
>> > will attach both versions.
>>
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104353] 3.7.0-rc4 #1 Not tainted
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104355] inconsistent
>> > {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104430]        CPU0
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104431]        ----
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104432]   
>> > lock(&(&ip->i_lock)->mr_lock);
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104433]   <Interrupt>
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104434]
>> > lock(&(&ip->i_lock)->mr_lock);
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104435]
>> > Nov  6 21:57:09 thoregon kernel: [ 9941.104435]  *** DEADLOCK ***
>>
>> Sorry! Copied the wrong report. Your fix only landed in -rc5, so my
>> vanilla -rc4 did (also) report the old problem again.
>> And I copy&pasted that report instead of the second appearance of the
>> new problem.
>
> Can you repost it with line wrapping turned off? The output simply
> becomes unreadable when it wraps....
>
> Yeah, I know I can put it back together, but I've got better things
> to do with my time than stitch a couple of hundred lines of debug
> back into a readable format....

Sorry about that, but I can't find any option to turn that off in Gmail.

I have added the reports as attachment, I hope thats OK for you.

Thanks for looking into this.

Torsten

Attachment: lockdep-reports.txt
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>