[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFx0j5QXCtHtZcc=JHkjW_vCB80j+fSer1B_fEqAaqDu=A@mail.gmail.com>
Date: Tue, 26 Nov 2013 14:30:10 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Josh Hunt <joshhunt00@...il.com>
Cc: Tejun Heo <tj@...nel.org>, Jonathan Nieder <jrnieder@...il.com>,
Ming Lei <ming.lei@...onical.com>,
Alex Riesen <raa.lkml@...il.com>,
Alan Stern <stern@...land.harvard.edu>,
Jens Axboe <axboe@...nel.dk>,
USB list <linux-usb@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [3.8-rc3 -> 3.8-rc4 regression] Re: [PATCH] module, async:
async_synchronize_full() on module init iff async is used
On Tue, Nov 26, 2013 at 2:12 PM, Josh Hunt <joshhunt00@...il.com> wrote:
>
> I should have clarified that I'm not using dm/md in my setup. I know
> the modules are getting loaded in the log I attached, but root is not
> a md/dm device.
Hmm. The initcall debugging doesn't actually show any of the "wait for
async events", because those debug messages come from
"do_one_initcall()", and the waiting happens later. Plus your messages
don't actually show where you are trying to - and failing - to mount
the root filesystem.
Without that kind of information, it's kind of hard to guess. Maybe
you could add a few printk's to your kernel? Add one to
do_init_module() *after* the
if (current->flags & PF_USED_ASYNC)
async_synchronize_full();
thing, and another to fs/namespace.c: do_mount() (just put something like
printk("do_mount: %s at %s\n", dev_name, dir_name);
or whatever, so that we can see when that happens..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists