public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: trond.myklebust@fys.uio.no
Cc: akpm@zip.com.au, aia21@cantab.net, linux-kernel@vger.kernel.org
Subject: Re: [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic
Date: Tue, 04 Jun 2002 03:39:03 -0700 (PDT)	[thread overview]
Message-ID: <20020604.033903.42777297.davem@redhat.com> (raw)
In-Reply-To: <200206041339.32899.trond.myklebust@fys.uio.no>

   From: Trond Myklebust <trond.myklebust@fys.uio.no>
   Date: Tue, 4 Jun 2002 13:39:32 +0200
   
   >From what I can see, the only other place where KM_USER0 is employed would be 
   in the *_highpage() helper routines in include/linux/highmem.h. These 
   routines are used in various places, but are usually not protected against 
   (soft and hard) interrupts or kernel pre-emption. Could it be that the latter 
   is what is causing trouble?

Any sort of interrupt whatsoever would be enough to cause a problem
here.  It is enough of a condition to allow the sunrpc code to
run.

This has nothing specific to do with preemption, although the fact
that KM_USER0 usage does not block preemption is worrysome.

  reply	other threads:[~2002-06-04 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  9:20 [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic Anton Altaparmakov
2002-06-03  9:48 ` Andrew Morton
2002-06-03 11:32   ` Trond Myklebust
2002-06-04  6:37     ` Andrew Morton
2002-06-04 11:39       ` Trond Myklebust
2002-06-04 10:39         ` David S. Miller [this message]
2002-06-04 12:10           ` Trond Myklebust
2002-06-04 11:46         ` Anton Altaparmakov

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=20020604.033903.42777297.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aia21@cantab.net \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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