All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: martin.wilck@ts.fujitsu.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	tpmdd-devel@lists.sourceforge.net,
	u.kleine-koenig@pengutronix.de
Subject: Re: [tpmdd-devel] [PATCH] base/platform: fix panic when probe function is NULL
Date: Sat, 28 Nov 2015 18:34:47 +0200	[thread overview]
Message-ID: <20151128163447.GD6518@intel.com> (raw)
In-Reply-To: <1448564494-23218-1-git-send-email-martin.wilck@ts.fujitsu.com>

On Thu, Nov 26, 2015 at 08:01:34PM +0100, martin.wilck@ts.fujitsu.com wrote:
> From: Martin Wilck <Martin.Wilck@ts.fujitsu.com>
> 
> Since b8b2c7d845d5, platform_drv_probe() is called for all platform
> devices. If drv->probe is NULL, and dev_pm_domain_attach() fails,
> platform_drv_probe() will return the error code from dev_pm_domain_attach().
> 
> This causes real_probe() to enter the "probe_failed" path and set
> dev->driver to NULL. Before b8b2c7d845d5, real_probe() would assume
> success if both dev->bus->probe and drv->probe are missing.
> 
> This may cause a panic later. For example, inserting the tpm_tis
> driver with parameter "force=1" (i.e. registering tpm_tis as a platform
> driver) will panic in tpmm_chip_alloc() because dev->driver is NULL:
> 
>      chip->cdev.owner = chip->pdev->driver->owner;
> 
> This patch fixes this by returning success in platform_drv_probe() if
> "just" dev_pm_domain_attach() had failed. This restores the semantics
> of platform_device_register_XXX() if the associated platform driver has
> no "probe" function.
> 
> Fixes: b8b2c7d845d5 ("base/platform: assert that dev_pm_domain
> callbacks are called unconditionally")
> 
> Signed-off-by: Martin Wilck <Martin.Wilck@ts.fujitsu.com>

Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

> ---
>  drivers/base/platform.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index 1dd6d3b..c994e76 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -513,10 +513,14 @@ static int platform_drv_probe(struct device *_dev)
>  		return ret;
>  
>  	ret = dev_pm_domain_attach(_dev, true);
> -	if (ret != -EPROBE_DEFER && drv->probe) {
> -		ret = drv->probe(dev);
> -		if (ret)
> -			dev_pm_domain_detach(_dev, true);
> +	if (ret != -EPROBE_DEFER) {
> +		if (drv->probe) {
> +			ret = drv->probe(dev);
> +			if (ret)
> +				dev_pm_domain_detach(_dev, true);
> +		} else
> +			/* don't fail if just dev_pm_domain_attach failed */
> +			ret = 0;
>  	}
>  
>  	if (drv->prevent_deferred_probe && ret == -EPROBE_DEFER) {
> -- 
> 1.8.3.1
> 
> 


  parent reply	other threads:[~2015-11-28 16:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 19:01 [PATCH] base/platform: fix panic when probe function is NULL martin.wilck
2015-11-26 20:30 ` [tpmdd-devel] " Jason Gunthorpe
2015-11-27  7:32   ` Wilck, Martin
2015-11-28 16:40   ` Jarkko Sakkinen
2015-11-28 16:49     ` Jarkko Sakkinen
2015-11-28 22:52     ` Jason Gunthorpe
2015-11-30 12:50       ` Jarkko Sakkinen
2015-11-27 10:11 ` Uwe Kleine-König
2015-11-30  7:42   ` Wilck, Martin
2015-11-30 11:50   ` [PATCH v2] base/platform: return success " martin.wilck
2015-12-01 20:30     ` Uwe Kleine-König
2015-12-01 10:41   ` [PATCH] base/platform: fix panic " Wilck, Martin
2015-12-01 13:24     ` Uwe Kleine-König
2015-12-01 15:19       ` Wilck, Martin
2015-12-01 17:25         ` [tpmdd-devel] " Jason Gunthorpe
2015-12-01 18:26           ` Peter Huewe
2015-12-01 18:40             ` Jason Gunthorpe
2015-12-01 18:54               ` Aw: " Peter Huewe
2015-12-01 19:03                 ` Jason Gunthorpe
2015-11-28 16:34 ` Jarkko Sakkinen [this message]
2015-11-29  9:54   ` Uwe Kleine-König
2015-11-30 12:56     ` Jarkko Sakkinen
2015-11-30 13:06       ` Jarkko Sakkinen

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=20151128163447.GD6518@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.wilck@ts.fujitsu.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.