From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Henri Roosen <henri.roosen@ginzinger.com>
Cc: linux-remoteproc@vger.kernel.org,
Ohad Ben-Cohen <ohad@wizery.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops
Date: Sun, 25 Jun 2017 14:51:48 -0700 [thread overview]
Message-ID: <20170625215148.GJ26155@builder> (raw)
In-Reply-To: <1496403321-32234-1-git-send-email-henri.roosen@ginzinger.com>
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.
(If this is not true there are a bunch of other places where this needs
to be checked as well)
Regards,
Bjorn
> Signed-off-by: Henri Roosen <henri.roosen@ginzinger.com>
> ---
> 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
>
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Henri Roosen <henri.roosen@ginzinger.com>
Cc: linux-remoteproc@vger.kernel.org,
Ohad Ben-Cohen <ohad@wizery.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops
Date: Sun, 25 Jun 2017 14:51:49 -0700 [thread overview]
Message-ID: <20170625215148.GJ26155@builder> (raw)
In-Reply-To: <1496403321-32234-1-git-send-email-henri.roosen@ginzinger.com>
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.
(If this is not true there are a bunch of other places where this needs
to be checked as well)
Regards,
Bjorn
> Signed-off-by: Henri Roosen <henri.roosen@ginzinger.com>
> ---
> 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
>
next prev parent reply other threads:[~2017-06-25 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:35 [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops Henri Roosen
2017-06-02 11:35 ` Henri Roosen
2017-06-02 21:47 ` Suman Anna
2017-06-02 21:47 ` Suman Anna
2017-06-25 21:51 ` Bjorn Andersson [this message]
2017-06-25 21:51 ` Bjorn Andersson
2017-06-26 9:04 ` Henri Roosen
2017-06-26 9:04 ` Henri Roosen
2017-06-28 19:24 ` Bjorn Andersson
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=20170625215148.GJ26155@builder \
--to=bjorn.andersson@linaro.org \
--cc=henri.roosen@ginzinger.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
/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.