From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Scott Branden <scott.branden@broadcom.com>,
Hans de Goede <hdegoede@redhat.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: Unsafe find_vpid() calls
Date: Thu, 28 Nov 2024 16:07:20 +0100 [thread overview]
Message-ID: <2024112853-conjure-posh-bf7a@gregkh> (raw)
In-Reply-To: <ueprb5sfjisjucekft3ls7it3pacq44ryfyqtumb3be3itmzy4@mnp4e2lcbzus>
On Thu, Nov 28, 2024 at 03:58:06PM +0100, Christian Brauner wrote:
> Hey,
>
> You have various calls to find_vpid() in your drivers that aren't
> protected by either tasklist_lock or rcu_read_lock(). Afair, this is
> unsafe as the struct pid might be freed beneath you. You should please
> fix those places to be protected by rcu_read_lock(). Something like the
> below or similar should work.
>
> Thanks!
> Christian
>
> diff --git a/drivers/misc/bcm-vk/bcm_vk_dev.c b/drivers/misc/bcm-vk/bcm_vk_dev.c
> index d4a96137728d..84cab909db71 100644
> --- a/drivers/misc/bcm-vk/bcm_vk_dev.c
> +++ b/drivers/misc/bcm-vk/bcm_vk_dev.c
> @@ -522,7 +522,9 @@ void bcm_vk_blk_drv_access(struct bcm_vk *vk)
> dev_dbg(&vk->pdev->dev,
> "Send kill signal to pid %d\n",
> ctx->pid);
> + rcu_read_lock();
> kill_pid(find_vpid(ctx->pid), SIGKILL, 1);
> + rcu_read_unlock();
> }
> }
> }
> diff --git a/drivers/misc/bcm-vk/bcm_vk_tty.c b/drivers/misc/bcm-vk/bcm_vk_tty.c
> index 59bab76ff0a9..6bd93347938e 100644
> --- a/drivers/misc/bcm-vk/bcm_vk_tty.c
> +++ b/drivers/misc/bcm-vk/bcm_vk_tty.c
> @@ -326,8 +326,11 @@ void bcm_vk_tty_terminate_tty_user(struct bcm_vk *vk)
>
> for (i = 0; i < BCM_VK_NUM_TTY; ++i) {
> vktty = &vk->tty[i];
> - if (vktty->pid)
> + if (vktty->pid) {
> + rcu_read_lock();
> kill_pid(find_vpid(vktty->pid), SIGKILL, 1);
> + rcu_read_unlock();
> + }
> }
> }
>
> diff --git a/drivers/staging/rtl8712/rtl8712_cmd.c b/drivers/staging/rtl8712/rtl8712_cmd.c
> index bb7db96ed821..de13f4eab60f 100644
> --- a/drivers/staging/rtl8712/rtl8712_cmd.c
> +++ b/drivers/staging/rtl8712/rtl8712_cmd.c
> @@ -61,7 +61,9 @@ static void check_hw_pbc(struct _adapter *padapter)
> */
> if (padapter->pid == 0)
> return;
> + rcu_read_lock();
> kill_pid(find_vpid(padapter->pid), SIGUSR1, 1);
> + rcu_read_unlock();
> }
> }
Odds are all of these usages can just be removed entirely, I'll add it
to the "todo" list of mine...
thanks!
greg k-h
prev parent reply other threads:[~2024-11-28 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 14:58 Christian Brauner
2024-11-28 15:07 ` Greg Kroah-Hartman [this message]
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=2024112853-conjure-posh-bf7a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brauner@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.branden@broadcom.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®