From: Igor Pylypiv <ipylypiv@google.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: dev: Fix memory leak when underlying adapter does not support I2C
Date: Fri, 8 Nov 2024 00:13:50 +0000 [thread overview]
Message-ID: <Zy1Xvk9YKrjqc4S7@google.com> (raw)
In-Reply-To: <jc76qean5mqxba4nh5qdocxhl5aa7r4epryyviqkyktbu6grog@u43wzsaki23k>
On Thu, Nov 07, 2024 at 06:14:29PM +0100, Andi Shyti wrote:
> Hi Igor,
>
> that's a good catch, but...
>
> On Thu, Nov 07, 2024 at 01:48:27AM +0000, Igor Pylypiv wrote:
> > i2cdev_ioctl_rdwr() receives a buffer which is allocated by the caller.
>
> This needs to be a bit re-written. In the commit log you should
> describe what the patch does. You are telling where the buffer is
> allocated.
I thought subject line covered what the patch does. Ack. I'll update
the commit message in v2.
>
> > Fixes: 97ca843f6ad3 ("i2c: dev: Check for I2C_FUNC_I2C before calling i2c_transfer")
> > Signed-off-by: Igor Pylypiv <ipylypiv@google.com>
> > ---
> > drivers/i2c/i2c-dev.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/i2c/i2c-dev.c b/drivers/i2c/i2c-dev.c
> > index 61f7c4003d2f..5d15519ef737 100644
> > --- a/drivers/i2c/i2c-dev.c
> > +++ b/drivers/i2c/i2c-dev.c
> > @@ -247,8 +247,10 @@ static noinline int i2cdev_ioctl_rdwr(struct i2c_client *client,
> > int i, res;
> >
> > /* Adapter must support I2C transfers */
> > - if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C))
> > + if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
> > + kfree(msgs);
> > return -EOPNOTSUPP;
>
> Please, don't free it here, free it where it has been allocated,
> i.e. in compat_i2cdev_ioctl().
>
Sounds good. I'll move kfree() in v2.
Thanks,
Igor
> Andi
>
> > + }
> >
> > data_ptrs = kmalloc_array(nmsgs, sizeof(u8 __user *), GFP_KERNEL);
> > if (data_ptrs == NULL) {
> > --
> > 2.47.0.277.g8800431eea-goog
> >
prev parent reply other threads:[~2024-11-08 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 1:48 Igor Pylypiv
2024-11-07 17:14 ` Andi Shyti
2024-11-08 0:13 ` Igor Pylypiv [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=Zy1Xvk9YKrjqc4S7@google.com \
--to=ipylypiv@google.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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®