From: Anton Ivanov <anton.ivanov@cambridgegreys.com> To: Geert Uytterhoeven <geert@linux-m68k.org>, Miaoqian Lin <linmq006@gmail.com> Cc: Richard Weinberger <richard@nod.at>, Johannes Berg <johannes@sipsolutions.net>, Jakub Kicinski <kuba@kernel.org>, "David S. Miller" <davem@davemloft.net>, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-um@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] um: vector: Fix memory leak in vector_config Date: Tue, 3 Jan 2023 10:28:41 +0000 [thread overview] Message-ID: <eaedf019-349c-c686-0f23-093371b4b61f@cambridgegreys.com> (raw) In-Reply-To: <CAMuHMdWFyKA7nUojivvTwWcmxaiUQifRRB=Kn1q-qzmn20Xkuw@mail.gmail.com> On 03/01/2023 08:00, Geert Uytterhoeven wrote: > Hi Miaoqian, > > On Thu, Dec 29, 2022 at 8:53 AM Miaoqian Lin <linmq006@gmail.com> wrote: >> kstrdup() return newly allocated copy of the string. >> Call kfree() to release the memory when after use. >> >> Fixes: 49da7e64f33e ("High Performance UML Vector Network Driver") >> Signed-off-by: Miaoqian Lin <linmq006@gmail.com> > Thanks for your patch! > >> --- a/arch/um/drivers/vector_kern.c >> +++ b/arch/um/drivers/vector_kern.c >> @@ -765,6 +765,7 @@ static int vector_config(char *str, char **error_out) >> >> parsed = uml_parse_vector_ifspec(params); >> >> + kfree(params); > Are you sure the memory pointed to by "params" is no longer used? > "parsed" seems to contain pointers pointing to (parts of) the string > pointed to by "params", so it cannot be freed. +1. I was just about to send the same comment. > >> if (parsed == NULL) { >> *error_out = "vector_config failed to parse parameters"; >> return -EINVAL; > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- Anton R. Ivanov Cambridgegreys Limited. Registered in England. Company Number 10273661 https://www.cambridgegreys.com/
WARNING: multiple messages have this Message-ID (diff)
From: Anton Ivanov <anton.ivanov@cambridgegreys.com> To: Geert Uytterhoeven <geert@linux-m68k.org>, Miaoqian Lin <linmq006@gmail.com> Cc: Richard Weinberger <richard@nod.at>, Johannes Berg <johannes@sipsolutions.net>, Jakub Kicinski <kuba@kernel.org>, "David S. Miller" <davem@davemloft.net>, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-um@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] um: vector: Fix memory leak in vector_config Date: Tue, 3 Jan 2023 10:28:41 +0000 [thread overview] Message-ID: <eaedf019-349c-c686-0f23-093371b4b61f@cambridgegreys.com> (raw) In-Reply-To: <CAMuHMdWFyKA7nUojivvTwWcmxaiUQifRRB=Kn1q-qzmn20Xkuw@mail.gmail.com> On 03/01/2023 08:00, Geert Uytterhoeven wrote: > Hi Miaoqian, > > On Thu, Dec 29, 2022 at 8:53 AM Miaoqian Lin <linmq006@gmail.com> wrote: >> kstrdup() return newly allocated copy of the string. >> Call kfree() to release the memory when after use. >> >> Fixes: 49da7e64f33e ("High Performance UML Vector Network Driver") >> Signed-off-by: Miaoqian Lin <linmq006@gmail.com> > Thanks for your patch! > >> --- a/arch/um/drivers/vector_kern.c >> +++ b/arch/um/drivers/vector_kern.c >> @@ -765,6 +765,7 @@ static int vector_config(char *str, char **error_out) >> >> parsed = uml_parse_vector_ifspec(params); >> >> + kfree(params); > Are you sure the memory pointed to by "params" is no longer used? > "parsed" seems to contain pointers pointing to (parts of) the string > pointed to by "params", so it cannot be freed. +1. I was just about to send the same comment. > >> if (parsed == NULL) { >> *error_out = "vector_config failed to parse parameters"; >> return -EINVAL; > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- Anton R. Ivanov Cambridgegreys Limited. Registered in England. Company Number 10273661 https://www.cambridgegreys.com/ _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-01-03 11:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-29 7:53 [PATCH] um: vector: Fix memory leak in vector_config Miaoqian Lin 2022-12-29 7:53 ` Miaoqian Lin 2023-01-03 8:00 ` Geert Uytterhoeven 2023-01-03 8:00 ` Geert Uytterhoeven 2023-01-03 10:28 ` Anton Ivanov [this message] 2023-01-03 10:28 ` Anton Ivanov 2023-01-03 12:16 ` Miaoqian Lin 2023-01-03 12:16 ` Miaoqian Lin 2023-01-03 13:06 ` Geert Uytterhoeven 2023-01-03 13:06 ` Geert Uytterhoeven
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=eaedf019-349c-c686-0f23-093371b4b61f@cambridgegreys.com \ --to=anton.ivanov@cambridgegreys.com \ --cc=davem@davemloft.net \ --cc=geert@linux-m68k.org \ --cc=johannes@sipsolutions.net \ --cc=kuba@kernel.org \ --cc=linmq006@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-um@lists.infradead.org \ --cc=richard@nod.at \ --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: linkBe 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.