From: Andrew Morton <akpm@zip.com.au>
To: ptb@it.uc3m.es
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: scheduling with io_lock held in 2.4.6
Date: Sun, 19 Aug 2001 15:47:00 -0700 [thread overview]
Message-ID: <3B8041E4.8D02A20B@zip.com.au> (raw)
In-Reply-To: "from (env: ptb) at Aug 19, 2001 06:38:18 pm" <200108191858.UAA01216@nbd.it.uc3m.es>
"Peter T. Breuer" wrote:
>
> I am now fairly certain that the schedule occured while
> blkdev_release_request was in a completely innocuous line
>
No - from your earlier trace it looks like what happened
was that you dereferenced a bad address in blkdev_release_request():
Unable to handle kernel paging request at virtual address 00002004
But when the kernel processes this error the last thing it
tries to do is to kill off the offending process by calling
do_exit(). But do_exit() calls schedule().
So if you take an oops in interrupt context you'll basically
always see the "scheduling in interrupt" thing. So don't
worry about it.
You need to find out why you're dereferencing a bad pointer
in blkdev_release_request().
-
next prev parent reply other threads:[~2001-08-19 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 18:58 scheduling with io_lock held in 2.4.6 Peter T. Breuer
2001-08-19 22:47 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-19 20:42 Manfred Spraul
[not found] <3B7EC41C.9811D384@zip.com.au>
2001-08-18 21:57 ` Peter T. Breuer
2001-08-18 22:13 ` Andrew Morton
2001-08-19 1:21 ` Peter T. Breuer
2001-08-19 16:38 ` Peter T. Breuer
2001-08-16 23:45 Peter T. Breuer
2001-08-17 0:08 ` Andrew Morton
2001-08-18 19:27 ` Peter T. Breuer
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=3B8041E4.8D02A20B@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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