Re: [PATCH #2] console lock grabbed too early in printk...

From: Jeff Garzik (jgarzik@mandrakesoft.mandrakesoft.com)
Date: Sun Jul 02 2000 - 10:07:16 EST


On Sun, 2 Jul 2000, Chris Lattner wrote:
> _YES_ and I found the deadlock. :) I'll describe it for you... it's the
> result of two seemingly innocuous things:

> 1. printk of arguments to the sys_access function
> 2. printk of mappings of vm pages

Not a deadlock, you are breaking rules. A simple "don't do that" fixes
the deadlock.

printk takes only kernel-space addresses. Don't expect it to page
anything in for you. That work should be done in your driver, BEFORE
calling printk.

In general, don't expect userspace addresses to be available without
help from uaccess.h or map_user_kiobuf...

        Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:11 EST