From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Diego Calleja <diegocg@teleline.es>,
John McGowan <jmcgowan@inch.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.8.1: memory leak? cdrecord problem?
Date: Thu, 26 Aug 2004 13:57:39 +0200 [thread overview]
Message-ID: <412DD033.6000903@bio.ifi.lmu.de> (raw)
In-Reply-To: <41281496.8080800@kolivas.org>
Hi,
Con Kolivas wrote:
>> Yes, there's a memory leak, you can try 2.6.8.1-mm3
>> or apply the fix yourself (I think it's this one:
>> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8.1/2.6.8.1-mm3/broken-out/bio_uncopy_user-mem-leak.patch
>> )
>
>
> That wont do by itself. It only fixes the memory leak. You _also_ need
> this patch for audio cds to not be stuffed:
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8.1/2.6.8.1-mm3/broken-out/bio_uncopy_user-mem-leak-fix.patch
it doesn't work, even with these two patches applied. I tried to burn
a DVD image (3.5GB) with kernel 2.6.8.1 including those patches and
again the memory run full until the kernel started killing processes.
Unfortunately the host always crashes before it writes the messages
to the log files, but I saw some messages about "cpu0..." and DMA.
I was running "cdrecord -sao dev=ATAPI:/dev/cdrecorder -v 2.4.img"
on a NEC ND1300A.
Can I debug/provide more info?
BTW, the bio.c from 2.6.9rc1 and 2.6.8.1 don't differ, so I assume it's
still unfixed in 2.6.9-rc1, too...?
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
next prev parent reply other threads:[~2004-08-26 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 17:26 kernel 2.6.8.1: memory leak? cdrecord problem? John McGowan
2004-08-21 17:44 ` Diego Calleja
2004-08-22 3:35 ` Con Kolivas
2004-08-26 11:57 ` Frank Steiner [this message]
2004-08-26 12:34 ` Frank Steiner
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=412DD033.6000903@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=diegocg@teleline.es \
--cc=jmcgowan@inch.com \
--cc=kernel@kolivas.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