All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix leak with bounced bio's
Date: Thu, 9 Sep 2004 16:36:56 +0200	[thread overview]
Message-ID: <20040909143656.GB1737@suse.de> (raw)
In-Reply-To: <414069DF.9000804@bio.ifi.lmu.de>

On Thu, Sep 09 2004, Frank Steiner wrote:
> Jens Axboe wrote:
> >Hi,
> >
> >This might fix the last leak of memory reported with cd writing, the
> >current highmem bounce code will leak n-1 pages for any n page bio where
> >n > 1. CD writing typically uses 16 pages bios, so it is affected.
> 
> 
> it fixes the leak for us that I described a while back
> http://marc.theaimsgroup.com/?l=linux-kernel&m=109360958318479&w=2
> 
> Great :-))

Great, thanks for confirming!

Maybe we should unconditionally bounce all bios for a while in a test
kernel, to make sure that all bouncing bugs are shaken out ;-)

-- 
Jens Axboe


      reply	other threads:[~2004-09-09 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  8:42 [PATCH] fix leak with bounced bio's Jens Axboe
2004-09-09 14:34 ` Frank Steiner
2004-09-09 14:36   ` Jens Axboe [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=20040909143656.GB1737@suse.de \
    --to=axboe@suse.de \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --cc=linux-kernel@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 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.