From: "Wilck, Martin" <martin.wilck@ts.fujitsu.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: Re: [PATCH] base/platform: fix panic when probe function is NULL
Date: Mon, 30 Nov 2015 08:42:16 +0100 [thread overview]
Message-ID: <C5A28EF7B98F574C85C70238C8E9ECC04E682BF141@ABGEX74E.FSC.NET> (raw)
In-Reply-To: <20151127101125.GS19888@pengutronix.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3841 bytes --]
Hello Uwe,
thanks for your review.
> 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 sounds like a separate issue though. Looking at init_tis there is:
>
> rc = platform_driver_register(&tis_drv);
> if (rc < 0)
> return rc;
> pdev = platform_device_register_simple("tpm_tis", -1, NULL, 0);
> if (IS_ERR(pdev)) {
> rc = PTR_ERR(pdev);
> goto err_dev;
> }
> rc = tpm_tis_init(&pdev->dev, &tis_default_info, NULL);
>
> tpm_tis_init calls tpmm_chip_alloc which barfs when pdev (i.e. the return value
> of platform_device_register_simple above) isn't bound. It is not allowed
> to assume that the device is bound after the above function calls.
I agree that the TPM platform device code deserves improvement. Jason
wrote that he has already some patches available for that.
I lack the knowledge to judge whether or not tpm_is_init's assumption
was correct. But, maybe just by luck, this assumption used to be *true*
until patch b8b2c7d845d5. Driver and device were matched by name
("tpm_tis") by the platform driver probing code, and device and driver
were actually bound to each other after this sequence of calls.
> So I'd say drop the paragraph about tpm_tis and the change is fine.
I didn't mean to blame your patch. But a note about the panic might be
helpful just in case someone else runs into the same problem. The
connection between your patch and tpm_tis loading is far from obvious.
I mentioned the panic in order to clarify that this wasn't just a
theoretical issue.
Anyway, I'll resubmit with your style hints applied and will try to find
a wording for the commit message that we can agree upon.
Best Regards,
Martin
>
> > 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")
> >
>
> I think line breaks in the Fixes: line are frowned on. Also usually
> there is no empty line between Fixes: and S-o-b:.
>
> > Signed-off-by: Martin Wilck <Martin.Wilck@ts.fujitsu.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;
>
> An else that has a } should also have a {, according to
> checkpatch and Documentation/CodingStyle. You can write it
> alternatively as:
>
> if (ret != -EPROBE_DEFER) {
> if (drv->probe)
> ret = drv->probe(dev);
> else
> ret = 0;
>
> if (ret)
> dev_pm_domain_detach(_dev, true);
> }
>
> .
>
> Best regards
> Uwe
>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-11-30 7:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 19:01 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 [this message]
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
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=C5A28EF7B98F574C85C70238C8E9ECC04E682BF141@ABGEX74E.FSC.NET \
--to=martin.wilck@ts.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®