From: Greg Afinogenov <antisthenes@inbox.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bio_uncopy_user mem leak
Date: Thu, 19 Aug 2004 04:59:58 -0500 [thread overview]
Message-ID: <1092909598.8364.5.camel@localhost> (raw)
I'd just like to point out that this patch does not, as may be expected,
result in functional audio CDs. It merely results in a successful burn
process and a CD full of noise.
Perhaps this should be tested/fixed?
Greg
(I'm not subscribed to this list; please CC me any responses; thanks!)
next reply other threads:[~2004-08-19 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 9:59 Greg Afinogenov [this message]
2004-08-19 11:07 ` [PATCH] bio_uncopy_user mem leak Con Kolivas
2004-08-19 13:51 ` Chris Mason
2004-08-19 19:55 ` Kurt Garloff
2004-08-20 3:19 ` Con Kolivas
2004-08-20 6:31 ` Andrew Morton
2004-08-20 12:54 ` Kurt Garloff
2004-08-20 20:28 ` sandr8
2004-08-20 7:15 ` Greg Afinogenov
2004-08-20 12:46 ` Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 15:59 Kurt Garloff
2004-08-17 21:08 ` Gene Heskett
2004-08-17 22:50 ` Andrew Morton
2004-08-19 7:16 ` Colin Leroy
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=1092909598.8364.5.camel@localhost \
--to=antisthenes@inbox.ru \
--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