public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Debug: sleeping function called from invalid context
Date: Mon, 18 Aug 2003 23:14:04 -0500	[thread overview]
Message-ID: <20030819041404.GI16387@waste.org> (raw)
In-Reply-To: <20030818203513.393c4a48.akpm@osdl.org>

On Mon, Aug 18, 2003 at 08:35:13PM -0700, Andrew Morton wrote:
> "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> >
> > Debug: sleeping function called with interrupts disabled at
> >  include/asm/uaccess.h:473
> 
> OK, now my vague understanding of what's going on is that the app has
> chosen to disable local interupts (via iopl()) and has taken a vm86 trap. 

Are you suggesting that whatever's calling sys_vm86 has disabled
interrupts beforehand? I don't see why that's necessary at all. The
vm86 fault handler is called via do_general_protection in any case and
as such is in_interrupt() by definition. And a vm86 general protection
fault can be caused by any of cli, sti, pushf, popf, intx, or iret. In
fact, typical usage of vm86 mode is to setup a call to a 16-bit
software interrupt handler and return via fault on the iret.

I'm increasingly convinced it's actually broken.

-- 
Matt Mackall : http://www.selenic.com : of or relating to the moon

  parent reply	other threads:[~2003-08-19  4:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 17:18 Debug: sleeping function called from invalid context Randy.Dunlap
2003-08-15 17:32 ` Dave Jones
2003-08-15 17:42   ` Randy.Dunlap
2003-08-15 19:30   ` Randy.Dunlap
2003-08-16  7:06     ` Matt Mackall
2003-08-18 21:07       ` Randy.Dunlap
2003-08-18 21:26         ` Matt Mackall
2003-08-19  0:13         ` Dave Jones
2003-08-19  0:15           ` Randy.Dunlap
2003-08-19  1:02             ` Zwane Mwaikambo
2003-08-19  0:15           ` Andrew Morton
2003-08-19  1:27             ` Matt Mackall
2003-08-19  3:24             ` Randy.Dunlap
2003-08-19  3:35               ` Andrew Morton
2003-08-19  3:39                 ` Randy.Dunlap
2003-08-19  4:26                   ` Matt Mackall
2003-08-19  4:29                   ` Andrew Morton
2003-08-19  4:14                 ` Matt Mackall [this message]
2003-08-19  5:14                 ` Matt Mackall
2003-08-19  1:01           ` Matt Mackall
2003-08-19  1:04             ` Dave Jones
2003-08-19  1:09               ` Matt Mackall

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=20030819041404.GI16387@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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