mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Mario Limonciello <mario_limonciello@dell.com>, ming.lei@canonical.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dell_rbu: Don't fallback to userhelper when loading firmware
Date: Mon, 16 May 2016 10:12:21 -0700	[thread overview]
Message-ID: <5137db8c-644e-3306-882c-cc820394cbce@redhat.com> (raw)
In-Reply-To: <1463413264-32500-1-git-send-email-mario_limonciello@dell.com>

On 05/16/2016 08:41 AM, Mario Limonciello wrote:
> dell_rbu previously would allow a userspace application to craft the
> payload after dell_rbu was loaded and abuse the udev userspace API.
>
> Instead require the payload to be crafted and placed in
> /lib/firmware/dell_rbu ahead of time.
>
> This adjusts dell_rbu to immediately load the firmware from
> /lib/firmware/dell_rbu when "init" is passed into image_type using the
> kernel helper.

Looks like you missed the Signed-off-by line.

Can you also drop the Kconfig dependency on CONFIG_FW_LOADER_USER_HELPER?

Thanks,
Laura

> ---
>  drivers/firmware/dell_rbu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/dell_rbu.c b/drivers/firmware/dell_rbu.c
> index d5f5b98..5ecf043 100644
> --- a/drivers/firmware/dell_rbu.c
> +++ b/drivers/firmware/dell_rbu.c
> @@ -677,7 +677,7 @@ static ssize_t write_rbu_image_type(struct file *filp, struct kobject *kobj,
>  		if (!rbu_data.entry_created) {
>  			spin_unlock(&rbu_data.lock);
>  			req_firm_rc = request_firmware_nowait(THIS_MODULE,
> -						      FW_ACTION_NOHOTPLUG,
> +						      FW_ACTION_HOTPLUG,
>  						      "dell_rbu",
>  						      &rbu_device->dev,
>  						      GFP_KERNEL,
>

  reply	other threads:[~2016-05-16 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 15:41 Mario Limonciello
2016-05-16 17:12 ` Laura Abbott [this message]
2016-05-16 17:43   ` Mario_Limonciello

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=5137db8c-644e-3306-882c-cc820394cbce@redhat.com \
    --to=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario_limonciello@dell.com \
    --cc=ming.lei@canonical.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 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®