From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Hangyu Hua <hbh25y@gmail.com>, asmadeus@codewreck.org
Cc: ericvh@kernel.org, lucho@ionkov.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jvrao@linux.vnet.ibm.com, v9fs@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: 9p: fix possible memory leak in p9_check_errors()
Date: Thu, 26 Oct 2023 15:18:16 +0200 [thread overview]
Message-ID: <2383398.41Bra3A7bo@silver> (raw)
In-Reply-To: <ZTpTU8-1zn_P22QX@codewreck.org>
On Thursday, October 26, 2023 1:53:55 PM CEST asmadeus@codewreck.org wrote:
>
> Hangyu Hua wrote on Thu, Oct 26, 2023 at 05:23:51PM +0800:
> > When p9pdu_readf is called with "s?d" attribute, it allocates a pointer
> > that will store a string. But when p9pdu_readf() fails while handling "d"
> > then this pointer will not be freed in p9_check_errors.
>
> Right, that sounds correct to me.
>
> Out of curiosity how did you notice this? The leak shouldn't happen with
> any valid server.
>
> This cannot break anything so I'll push this to -next tomorrow and
> submit to Linus next week
>
> > Fixes: ca41bb3e21d7 ("[net/9p] Handle Zero Copy TREAD/RERROR case in !dotl case.")
>
> This commit moves this code a bit, but the p9pdu_readf call predates
> it -- in this case the Fixes tag is probably not useful; this affects
> all maintained kernels.
Looks like it exists since introduction of p9_check_errors(), therefore:
Fixes: 51a87c552dfd ("9p: rework client code to use new protocol support functions")
> > Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
> > ---
> > net/9p/client.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/net/9p/client.c b/net/9p/client.c
> > index 86bbc7147fc1..6c7cd765b714 100644
> > --- a/net/9p/client.c
> > +++ b/net/9p/client.c
> > @@ -540,12 +540,15 @@ static int p9_check_errors(struct p9_client *c, struct p9_req_t *req)
> > return 0;
> >
> > if (!p9_is_proto_dotl(c)) {
> > - char *ename;
> > + char *ename = NULL;
> >
> > err = p9pdu_readf(&req->rc, c->proto_version, "s?d",
> > &ename, &ecode);
> > - if (err)
> > + if (err) {
> > + if (ename != NULL)
> > + kfree(ename);
>
> Don't check for NULL before kfree - kfree does it.
> If that's the only remark you get I can fix it when applying the commit
> on my side.
With those two remarks addressed:
Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
>
>
> > goto out_err;
> > + }
> >
> > if (p9_is_proto_dotu(c) && ecode < 512)
> > err = -ecode;
>
>
next prev parent reply other threads:[~2023-10-26 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:23 [PATCH] net: 9p: fix possible memory leak in p9_check_errors() Hangyu Hua
2023-10-26 11:53 ` asmadeus
2023-10-26 13:18 ` Christian Schoenebeck [this message]
2023-10-27 2:41 ` Hangyu Hua
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=2383398.41Bra3A7bo@silver \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@kernel.org \
--cc=hbh25y@gmail.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=v9fs@lists.linux.dev \
/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 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.