From: PanBian <bianpan2016@163.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH V2] block/bio-integrity: fix mismatched alloc free
Date: Mon, 19 Aug 2019 12:14:39 +0800 [thread overview]
Message-ID: <20190819041439.GA23459@sise> (raw)
In-Reply-To: <20190819035613.GC3086@ming.t460p>
On Mon, Aug 19, 2019 at 11:56:14AM +0800, Ming Lei wrote:
> On Mon, Aug 19, 2019 at 08:59:13AM +0800, Pan Bian wrote:
> > The function kmalloc rather than mempool_alloc is called to allocate
> > memory when the memory pool is unavailable. However, mempool_alloc is
> > used to release the memory chunck in both cases when error occurs. This
> > patch fixes the bug.
> >
> > Fixes: 9f060e2231c ("block: Convert integrity to bvec_alloc_bs()")
> > Signed-off-by: Pan Bian <bianpan2016@163.com>
> > Cc: stable@vger.kernel.org
> > ---
> > V2: add Fixes and CC tags
> > ---
> > block/bio-integrity.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/block/bio-integrity.c b/block/bio-integrity.c
> > index fb95dbb..011dfc8 100644
> > --- a/block/bio-integrity.c
> > +++ b/block/bio-integrity.c
> > @@ -75,7 +75,10 @@ struct bio_integrity_payload *bio_integrity_alloc(struct bio *bio,
> >
> > return bip;
> > err:
> > - mempool_free(bip, &bs->bio_integrity_pool);
> > + if (!bs || !mempool_initialized(&bs->bio_integrity_pool))
> > + kfree(bip);
> > + else
> > + mempool_free(bip, &bs->bio_integrity_pool);
> > return ERR_PTR(-ENOMEM);
> > }
> > EXPORT_SYMBOL(bio_integrity_alloc);
>
> 'err' is still reached in case that 'bs' is valid, so fix nothing.
You are right! It's my fault.
Thanks,
Pan
>
>
> Thanks,
> Ming
prev parent reply other threads:[~2019-08-19 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 0:59 [PATCH V2] block/bio-integrity: fix mismatched alloc free Pan Bian
2019-08-19 3:56 ` Ming Lei
2019-08-19 4:14 ` PanBian [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=20190819041439.GA23459@sise \
--to=bianpan2016@163.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).