On 06/25/2017 11:51 PM, Bjorn Andersson wrote:
On Fri 02 Jun 04:35 PDT 2017, Henri Roosen wrote:
A device might not have an ops structure registered. This
patch fixes a null-prt dereference by checking ops before dereferencing
it.
In what scenario do you end up with a rpdev without ops defined?
You need at least create_ept defined in your ops to be able to do any
form of communication. So it would probably make more sense to add a
sanity check in rpmsg_register_device(), but perhaps I'm missing
something.
I was trying to add support for the generic rpmsg-char driver for
virtio_rpmsg_bus.
The rpmsg-char driver gets registered using
rpmsg_chrdev_register_device(), and IMHO this device should not have any
.ops. The chrdev is not used for communication, only for creating
devices. The devices which should have the .ops are the ones created
using the rpmsg-char device.
So actually having .ops for the device passed to
rpmsg_chrdev_register_device() in drivers/rpmsg/qcom_smd.c seems wrong
to me too and should be cleaned up.
(If this is not true there are a bunch of other places where this needs
to be checked as well)
If you agree to my opinion above, then I think this comes down to a
design decision: a possibility might be to split off the chrdev code to
a different implementation as the code for the communication devices.
Else we need to identify the other places for the check.
Best regards,
Henri
Regards,
Bjorn
Signed-off-by: Henri Roosen <henri.roosen@xxxxxxxxxxxxx>
---
drivers/rpmsg/rpmsg_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
index 600f5f9..0c48452 100644
--- a/drivers/rpmsg/rpmsg_core.c
+++ b/drivers/rpmsg/rpmsg_core.c
@@ -429,7 +429,7 @@ static int rpmsg_dev_probe(struct device *dev)
goto out;
}
- if (rpdev->ops->announce_create)
+ if (rpdev->ops && rpdev->ops->announce_create)
err = rpdev->ops->announce_create(rpdev);
out:
return err;
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
