From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@arm.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] drivercore: Fix ordering between deferred_probe and exiting initcalls
Date: Thu, 14 Feb 2013 10:28:24 -0800 [thread overview]
Message-ID: <20130214182824.GA20163@kroah.com> (raw)
In-Reply-To: <1360865667-8353-1-git-send-email-grant.likely@secretlab.ca>
On Thu, Feb 14, 2013 at 06:14:27PM +0000, Grant Likely wrote:
> One of the side effects of deferred probe is that some drivers which
> used to be probed before initcalls completed are now happening slightly
> later. This causes two problems.
> - If a console driver gets deferred, then it may not be ready when
> userspace starts. For example, if a uart depends on pinctrl, then the
> uart will get deferred and /dev/console will not be available
> - __init sections will be discarded before built-in drivers are probed.
> Strictly speaking, __init functions should not be called in a drivers
> __probe path, but there are a lot of drivers (console stuff again)
> that do anyway. In the past it was perfectly safe to do so because all
> built-in drivers got probed before the end of initcalls.
>
> This patch fixes the problem by forcing the first pass of the deferred
> list to complete at late_initcall time. This is late enough to catch the
> drivers that are known to have the above issues.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> Tested-by: Haojian Zhuang <haojian.zhuang@linaro.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: stable@vger.kernel.org
> ---
>
> Hi Greg and Linus,
>
> Okay, so this is really late to be sending for v3.8, and it doesn't have
> nearly the amount of testing that I would like it to have. I haven't
> even put it into linux-next yet. However, it is a real bug that some of
> the Linaro folks have run into that is caused by deferred probe. It
> isn't very widespread, but it is there.
>
> It probably should be in v3.8, but given how ridiculously late it is and
> that it isn't a widespread problem it would probably be just fine to go
> in during the v3.9 merge window and get backported to linux-stable. If I
> don't hear otherwise then that is what I'll do.
>
> Still, here it is. If you think it really should be merged before
> tagging v3.8 then please go ahead and apply it.
Nah, we can wait for 3.9-rc1, I'll queue it up in my tree and push it to
Linus for then, and tag it for stable kernels to be backported at that
point in time.
thanks,
greg k-h
prev parent reply other threads:[~2013-02-14 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 18:14 [PATCH] drivercore: Fix ordering between deferred_probe and exiting initcalls Grant Likely
2013-02-14 18:28 ` Greg Kroah-Hartman [this message]
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=20130214182824.GA20163@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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