mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Con Kolivas <kernel@kolivas.org>, Chris Mason <mason@suse.com>,
	Olaf Kirch <okir@suse.de>,
	antisthenes@inbox.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bio_uncopy_user mem leak
Date: Fri, 20 Aug 2004 14:54:16 +0200	[thread overview]
Message-ID: <20040820125416.GB12396@tpkurt.garloff.de> (raw)
In-Reply-To: <20040819233155.68c1411e.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

Hi Andrew,

On Thu, Aug 19, 2004 at 11:31:55PM -0700, Andrew Morton wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
> >
> >  Andrew did you threaten to make a 2.6.8.2 since 2.6.8{,.1} cannot safely 
> >  burn an audio cd?
> 
> Uh, I guess that depends on how rested Linus feels when he returns.  I
> think there's a fairly significant networking fix too.  As I said: we'll see.

I must have overlooked the network thing. But in internal testing we do 
see problems with 2.6.8, which seem to be related to networking and/or 
NFS.

Care to work out?

Regards,
-- 
Kurt Garloff, Director SUSE Labs, Novell Inc.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-20 12:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19  9:59 Greg Afinogenov
2004-08-19 11:07 ` 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 [this message]
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=20040820125416.GB12396@tpkurt.garloff.de \
    --to=garloff@suse.de \
    --cc=akpm@osdl.org \
    --cc=antisthenes@inbox.ru \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=okir@suse.de \
    /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

all inboxes | Powered by JetHome®