All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH 2.4.21-rc4] Fix oom killer braindamage
Date: Tue, 27 May 2003 21:34:39 +0200	[thread overview]
Message-ID: <20030527193439.GU845@suse.de> (raw)
In-Reply-To: <200305272130.43814.m.c.p@wolk-project.de>

On Tue, May 27 2003, Marc-Christian Petersen wrote:
> On Tuesday 27 May 2003 21:18, Marc-Christian Petersen wrote:
> 
> Hi again ^3 ;)
> 
> > > Not suitable for -rc. Btw, -rc5 is already at bkbits.net.
> Please, if there is any chance we can fix the pause/stop bug, delay .21 final 
> for some hours or a day (or maybe two)
> 
> I've CC'ed akpm and Axboe. I think they are the only ones knowing enough about 
> the code to see an obvious error and even fixing the bug?!
> 
> Do you agree? Does anyone else agree? Or disagree?

I have to agree with Marcelo, nothing in ll_rw_blk is obvious enough to
just be changed at will in -rc5 time.

I need to catch up with this thread, hopefully we can get things fixed
around 2.4.22-early.

-- 
Jens Axboe


  parent reply	other threads:[~2003-05-27 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 19:05 [PATCH 2.4.21-rc4] Fix oom killer braindamage Marc-Christian Petersen
2003-05-27 19:12 ` Marcelo Tosatti
2003-05-27 19:18   ` Marc-Christian Petersen
2003-05-27 19:28     ` Marc-Christian Petersen
2003-05-27 19:31       ` Marcelo Tosatti
2003-05-28 22:14         ` Pavel Machek
2003-05-27 19:31     ` Marc-Christian Petersen
2003-05-27 19:34       ` Marcelo Tosatti
2003-05-27 19:46         ` Marc-Christian Petersen
2003-05-27 19:34       ` Jens Axboe [this message]
2003-05-27 19:20 ` William Lee Irwin III

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=20030527193439.GU845@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=marcelo@conectiva.com.br \
    /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.