[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131204231212.GB10785@mtj.dyndns.org>
Date: Wed, 4 Dec 2013 18:12:12 -0500
From: Tejun Heo <tj@...nel.org>
To: Josh Hunt <joshhunt00@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.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
Hello, Josh.
On Wed, Dec 04, 2013 at 05:01:53PM -0600, Josh Hunt wrote:
> So there used to be a call to async_synchronize_full() in
> ata_host_register(), but it was removed by
> f29d3b23238e1955a8094e038c72546e99308e61 as part of some fastboot
> changes. Adding it back (in the attached patch) seems to resolve the
> issue when using the broken initrd. I'm guessing adding it back isn't
> an option, but I wanted to point it out.
The problem is that really isn't the root cause of it. There's no
real interlocking there and the problem gets hidden just because
things are slower. Putting ssleep(2) there would work the same, so
the true issue is "the kernel is faster with probing now", which is
somewhat challenging to rectify. :(
Thanks.
--
tejun
--
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