From: Jens Axboe <axboe@suse.de>
To: TazForEver@dlfp.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc1
Date: Wed, 8 Sep 2004 18:05:27 +0200 [thread overview]
Message-ID: <20040908160527.GS2258@suse.de> (raw)
In-Reply-To: <20040908155742.GA19335@elektroni.ee.tut.fi>
On Wed, Sep 08 2004, Petri Kaukasoina wrote:
> On Wed, Sep 08, 2004 at 05:34:39PM +0200, Jens Axboe wrote:
> > On Wed, Sep 08 2004, Benoit Dejean wrote:
> > > is it normal that 2.6.9-rc1 still leaks like hell when burning an audio
> > > CD ? i though this was fixed since 2.6.8.1
> >
> > hmm no, it should not be. more details, please.
>
> bio_uncopy_user-mem-leak-fix.patch and bio_uncopy_user-mem-leak.patch were
> not included in 2.6.9-rc1.
oh right you are, I forget that the -rc1 is already so old. so the
problem is expected, upgrade to latest -rc1-bkX and you'll be fine.
--
Jens Axboe
next prev parent reply other threads:[~2004-09-08 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 14:58 2.6.9-rc1 Benoit Dejean
2004-09-08 15:34 ` 2.6.9-rc1 Jens Axboe
2004-09-08 15:57 ` 2.6.9-rc1 Petri Kaukasoina
2004-09-08 16:05 ` Jens Axboe [this message]
2004-09-08 16:30 ` 2.6.9-rc1 Benoit Dejean
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 13:41 2.6.9-rc1 Sid Boyce
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=20040908160527.GS2258@suse.de \
--to=axboe@suse.de \
--cc=TazForEver@dlfp.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox