From: Al Viro <viro@ZenIV.linux.org.uk>
To: wfg@linux.intel.com
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel boot hangs on commit "switch fput to task_work_add"
Date: Sat, 14 Jul 2012 14:05:10 +0100 [thread overview]
Message-ID: <20120714130510.GC31729@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120710141830.GA5385@localhost>
On Tue, Jul 10, 2012 at 10:18:30PM +0800, wfg@linux.intel.com wrote:
> Hi Al,
>
> The linux-next kernel reliably hung after this line:
>
> [ 4.846260] debug: unmapping init [mem 0xffff88000182a000-0xffff8800019fffff]
>
> And it's bisected to commit:
>
> commit 4a9ffe81385c2af04f296bea05482f34e02ea10d
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Sun Jun 24 09:56:45 2012 +0400
>
> switch fput to task_work_add
>
> ... and schedule_work() for interrupt/kernel_thread callers
> (and yes, now it *is* OK to call from interrupt).
>
> I tried add this debug aid:
>
> init_post(void):
> + printk(KERN_WARNING "flush_delayed_fput\n");
> flush_delayed_fput();
> + printk(KERN_WARNING "flush_delayed_fput done\n");
>
> And then it hangs after "flush_delayed_fput done". So it's not directly
> freezing inside flush_delayed_fput()..
Could you post a stack trace, etc.? I'll try to reproduce that one, obviously,
but...
next prev parent reply other threads:[~2012-07-14 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 14:18 Kernel boot hangs on commit "switch fput to task_work_add" wfg
2012-07-12 13:46 ` Fengguang Wu
2012-07-14 13:05 ` Al Viro [this message]
2012-07-14 13:09 ` Fengguang Wu
2012-07-14 13:48 ` Fengguang Wu
2012-07-14 13:58 ` Fengguang Wu
2012-07-14 14:14 ` Al Viro
2012-07-14 14:34 ` Fengguang Wu
2012-07-14 15:19 ` Al Viro
2012-07-14 15:29 ` Fengguang Wu
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=20120714130510.GC31729@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wfg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).