[lkml]   [2001]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: scheduling with io_lock held in 2.4.6
"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().

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:57    [W:0.096 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site