All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc. kernel preemption bits
Date: 29 Aug 2002 15:11:26 -0400	[thread overview]
Message-ID: <1030648286.979.2597.camel@phantasy> (raw)
In-Reply-To: <3D6E66D5.A97E5CF3@zip.com.au>

On Thu, 2002-08-29 at 14:24, Andrew Morton wrote:

> Robert Love wrote:
> > 
> > ...
> >         - we have a debug check in preempt_schedule that, even
> >           on detecting a schedule with irqs disabled, still goes
> >           ahead and reschedules.  We should return. (me)
> > 
> 
> OK, but that warning will still come out of the mess in mm/slab.c.

Yah I saw your previous post.  There is also a report or two re oops on
poisoned memory with SLAB_DEBUG and preempt enabled - which should be
fixed by the above return but one report says it does not.

Anyhow, your new methods are fine... if they work, they work.

I am starting to get concerned over the number of routines we are having
to define.  It is getting complicated (i.e. the
inc_preempt_non_preempt() stuff).

Maybe keep these local to mm/slab.c ?

	Robert Love


  reply	other threads:[~2002-08-29 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 15:33 [PATCH] misc. kernel preemption bits Robert Love
2002-08-29 18:24 ` Andrew Morton
2002-08-29 19:11   ` Robert Love [this message]
2002-08-29 21:07     ` george anzinger
2002-08-29 18:38 ` Linus Torvalds
2002-08-29 18:39   ` Robert Love

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=1030648286.979.2597.camel@phantasy \
    --to=rml@tech9.net \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.