From: Lee Jones <lee@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mailbox: mailbox-test: fix a locking issue in mbox_test_message_write()
Date: Wed, 31 May 2023 09:52:43 +0100 [thread overview]
Message-ID: <20230531085243.GB449117@google.com> (raw)
In-Reply-To: <c3b517eb-3805-48bf-be89-0082bff65913@kili.mountain>
Jassi,
On Fri, 05 May 2023, Dan Carpenter wrote:
> There was a bug where this code forgot to unlock the tdev->mutex if the
> kzalloc() failed. Fix this issue, by moving the allocation outside the
> lock.
>
> Fixes: 2d1e952a2b8e ("mailbox: mailbox-test: Fix potential double-free in mbox_test_message_write()")
When are you planning on sending this to the -rcs?
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> drivers/mailbox/mailbox-test.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mailbox/mailbox-test.c b/drivers/mailbox/mailbox-test.c
> index c4a705c30331..fc6a12a51b40 100644
> --- a/drivers/mailbox/mailbox-test.c
> +++ b/drivers/mailbox/mailbox-test.c
> @@ -98,6 +98,7 @@ static ssize_t mbox_test_message_write(struct file *filp,
> size_t count, loff_t *ppos)
> {
> struct mbox_test_device *tdev = filp->private_data;
> + char *message;
> void *data;
> int ret;
>
> @@ -113,12 +114,13 @@ static ssize_t mbox_test_message_write(struct file *filp,
> return -EINVAL;
> }
>
> - mutex_lock(&tdev->mutex);
> -
> - tdev->message = kzalloc(MBOX_MAX_MSG_LEN, GFP_KERNEL);
> - if (!tdev->message)
> + message = kzalloc(MBOX_MAX_MSG_LEN, GFP_KERNEL);
> + if (!message)
> return -ENOMEM;
>
> + mutex_lock(&tdev->mutex);
> +
> + tdev->message = message;
> ret = copy_from_user(tdev->message, userbuf, count);
> if (ret) {
> ret = -EFAULT;
> --
> 2.39.2
>
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-05-31 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 9:22 [PATCH] mailbox: mailbox-test: fix a locking issue in mbox_test_message_write() Dan Carpenter
2023-05-10 13:35 ` Lee Jones
2023-05-31 8:52 ` Lee Jones [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=20230531085243.GB449117@google.com \
--to=lee@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=jassisinghbrar@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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