From: Jens Axboe <jens.axboe@oracle.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, martin.petersen@oracle.com
Subject: Re: [PATCH] block: fix memory leak in bio_clone()
Date: Mon, 9 Mar 2009 10:54:11 +0100 [thread overview]
Message-ID: <20090309095411.GL11787@kernel.dk> (raw)
In-Reply-To: <49B4E6AE.2030302@cn.fujitsu.com>
On Mon, Mar 09 2009, Li Zefan wrote:
> >>> as the mempool mask. So the leak will not occur, but it does mean that
> >>> it isn't honoring the gfp_mask passed in to bio_clone(), which is the
> >> I noticed there was a patch to do this, and seems you planed to merge
> >> it into .29?
> >>
> >> "[PATCH] Add gfp_mask to bio_integrity_clone()"
> >>
> >> http://lkml.org/lkml/2008/10/30/11
> >
> > Hmm strange, apparently that never got queued up and I had forgotten all
> > about that issue until your email. I'll add it asap.
> >
>
> I found bio_integrity_clone() is not using the gfp_mask passed by bio_clone(),
> so I googled it in LKML before I fix it. :)
I've got both patches queued up now:
http://git.kernel.dk/?p=linux-2.6-block.git;a=shortlog;h=refs/heads/for-linus
> >>> first bug. The second bug is that it should be using its own bioset, as
> >>> it is illegal to do multiple __GFP_WAIT allocations on a single mempool
> >>> and always expect progress.
> >
> > That one still stands.
> >
>
> Yes, and I'd leave it to you or Martin. ;)
I'll let Martin sort that out, it can easily wait for the next release.
--
Jens Axboe
next prev parent reply other threads:[~2009-03-09 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 9:13 [PATCH] block: fix memory leak in bio_clone() Li Zefan
2009-03-09 9:21 ` Li Zefan
2009-03-09 9:24 ` Jens Axboe
2009-03-09 9:34 ` Li Zefan
2009-03-09 9:38 ` Jens Axboe
2009-03-09 9:51 ` Li Zefan
2009-03-09 9:54 ` Jens Axboe [this message]
2009-03-09 16:10 ` Martin K. Petersen
2009-03-09 19:21 ` Jens Axboe
2009-03-10 3:42 ` Martin K. Petersen
2009-03-10 7:29 ` Jens Axboe
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=20090309095411.GL11787@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=martin.petersen@oracle.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.