From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zram: fix possible use after free in zcomp_create()
Date: Mon, 7 Sep 2015 22:33:32 +0900 [thread overview]
Message-ID: <20150907133332.GA539@swordfish> (raw)
In-Reply-To: <20150907125343.GG10075@ares>
On (09/07/15 13:53), Luis Henriques wrote:
> > On (09/07/15 11:33), Luis Henriques wrote:
> > > zcomp_create() verifies the success of zcomp_strm_{multi,siggle}_create()
> > > through comp->stream, which can potentially be pointing to memory that was
> > > freed if these functions returned an error.
> > >
> >
> > good catch.
> >
> > we probably better start checking the zcomp_strm_multi_create()/
> > zcomp_strm_single_create() status in zcomp_create(); that's much
> > more obvious and that's why we return it in the first place.
> >
> > what do you think?
> >
>
> Yep, that's probably a better solution.
>
> Acked-by: Luis Henriques <luis.henriques@canonical.com>
>
Oh, thanks. I don't mind if you will re-submit it; I just did minor
changes to our fix. Or I can handle it. I'm OK with either way. Btw,
did you hit that problem or you reviewed the code?
-ss
> Cheers,
> --
> Luís
>
> > ---
> >
> > drivers/block/zram/zcomp.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/block/zram/zcomp.c b/drivers/block/zram/zcomp.c
> > index 3456d5a..16bbc8c 100644
> > --- a/drivers/block/zram/zcomp.c
> > +++ b/drivers/block/zram/zcomp.c
> > @@ -360,6 +360,7 @@ struct zcomp *zcomp_create(const char *compress, int max_strm)
> > {
> > struct zcomp *comp;
> > struct zcomp_backend *backend;
> > + int ret;
> >
> > backend = find_backend(compress);
> > if (!backend)
> > @@ -371,10 +372,10 @@ struct zcomp *zcomp_create(const char *compress, int max_strm)
> >
> > comp->backend = backend;
> > if (max_strm > 1)
> > - zcomp_strm_multi_create(comp, max_strm);
> > + ret = zcomp_strm_multi_create(comp, max_strm);
> > else
> > - zcomp_strm_single_create(comp);
> > - if (!comp->stream) {
> > + ret = zcomp_strm_single_create(comp);
> > + if (ret != 0) {
> > kfree(comp);
> > return ERR_PTR(-ENOMEM);
> > }
> >
>
next prev parent reply other threads:[~2015-09-07 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 10:33 [PATCH] zram: fix possible use after free in zcomp_create() Luis Henriques
2015-09-07 11:11 ` Sergey Senozhatsky
2015-09-07 12:53 ` Luis Henriques
2015-09-07 13:33 ` Sergey Senozhatsky [this message]
2015-09-07 14:11 ` Luis Henriques
2015-09-07 14:13 ` [PATCH v2] " Luis Henriques
2015-09-07 23:59 ` Sergey Senozhatsky
2015-09-08 1:07 ` Minchan Kim
2015-09-08 1:20 ` Sergey Senozhatsky
2015-09-08 1:34 ` Minchan Kim
2015-09-08 9:39 ` [PATCH v3] " Luis Henriques
2015-09-08 9:56 ` Sergey Senozhatsky
2015-09-08 10:27 ` Sergey Senozhatsky
2015-09-08 13:35 ` Minchan Kim
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=20150907133332.GA539@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.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 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.