All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Suman Anna <s-anna@ti.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	Loic Pallardy <loic.pallardy@st.com>,
	Arnaud Pouliquen <arnaud.pouliquen@st.com>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] remoteproc: Check for NULL firmwares in sysfs interface
Date: Fri, 5 Oct 2018 23:14:03 -0700	[thread overview]
Message-ID: <20181006061403.GD12063@builder> (raw)
In-Reply-To: <20180915003725.17549-3-s-anna@ti.com>

On Fri 14 Sep 17:37 PDT 2018, Suman Anna wrote:

> The remoteproc framework provides a sysfs file 'firmware'
> for modifying the firmware image name from userspace. Add
> an additional check to ensure NULL firmwares are errored
> out right away, rather than getting a delayed error while
> requesting a firmware during the start of a remoteproc
> later on.
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>

Applied.

Regards,
Bjorn

> ---
>  drivers/remoteproc/remoteproc_sysfs.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/remoteproc/remoteproc_sysfs.c b/drivers/remoteproc/remoteproc_sysfs.c
> index 2142b3ea726e..ce93f4d710f3 100644
> --- a/drivers/remoteproc/remoteproc_sysfs.c
> +++ b/drivers/remoteproc/remoteproc_sysfs.c
> @@ -49,6 +49,11 @@ static ssize_t firmware_store(struct device *dev,
>  	}
>  
>  	len = strcspn(buf, "\n");
> +	if (!len) {
> +		dev_err(dev, "can't provide a NULL firmware\n");
> +		err = -EINVAL;
> +		goto out;
> +	}
>  
>  	p = kstrndup(buf, len, GFP_KERNEL);
>  	if (!p) {
> -- 
> 2.18.0
> 

  parent reply	other threads:[~2018-10-06  6:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15  0:37 [PATCH 0/5] remoteproc sysfs fixes/improvements Suman Anna
2018-09-15  0:37 ` Suman Anna
2018-09-15  0:37 ` [PATCH 1/5] remoteproc: Fix unbalanced boot with sysfs for no auto-boot rprocs Suman Anna
2018-09-15  0:37   ` Suman Anna
2018-10-02  9:27   ` Arnaud Pouliquen
2018-10-02  9:27     ` Arnaud Pouliquen
2018-10-06  6:13   ` Bjorn Andersson
2018-10-08 16:42     ` Suman Anna
2018-10-08 16:42       ` Suman Anna
2018-09-15  0:37 ` [PATCH 2/5] remoteproc: Check for NULL firmwares in sysfs interface Suman Anna
2018-09-15  0:37   ` Suman Anna
2018-10-02  9:43   ` Arnaud Pouliquen
2018-10-02  9:43     ` Arnaud Pouliquen
2018-10-02 15:05     ` Suman Anna
2018-10-02 15:05       ` Suman Anna
2018-10-06  6:14   ` Bjorn Andersson [this message]
2018-09-15  0:37 ` [PATCH 3/5] remoteproc: Add missing kernel-doc comment for auto-boot Suman Anna
2018-09-15  0:37   ` Suman Anna
2018-10-06  6:14   ` Bjorn Andersson
2018-09-15  0:37 ` [PATCH 4/5] remoteproc: Introduce deny_sysfs_ops flag Suman Anna
2018-09-15  0:37   ` Suman Anna
2018-10-02  9:47   ` Arnaud Pouliquen
2018-10-02  9:47     ` Arnaud Pouliquen
2018-10-02 15:14     ` Suman Anna
2018-10-02 15:14       ` Suman Anna
2018-09-15  0:37 ` [PATCH 5/5] remoteproc/wkup_m3: Set " Suman Anna
2018-09-15  0:37   ` Suman Anna
2018-10-01 21:11 ` [PATCH 0/5] remoteproc sysfs fixes/improvements Suman Anna
2018-10-01 21:11   ` Suman Anna

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=20181006061403.GD12063@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=ohad@wizery.com \
    --cc=s-anna@ti.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.