On Tue, Mar 20, 2007 at 01:08:23AM +0800, Daniel Cheng wrote:
>
> Here are something interesting:
>
> > Mar 19 00:42:08 localhost kernel: [ 395.698137] [<e07d9000>] init_module+0x0/0x10 [faulty_int]
>
> we have ignore_int here:
>
> > Mar 19 00:42:08 localhost kernel: [ 395.698152] [<c03ce23d>] ignore_int+0x1/0x44
> > Mar 19 00:42:08 localhost kernel: [ 395.698164] [<e07d9002>]
> init_module+0x2/0x10 [faulty_int]
>
> I guess the kernel just don't expect an interrupt in init_module?
>
Sounded reasonable till I tried to put the INT instruction in a
char device write() function then issuing $echo "HI" > /dev/faulty
command, which generated the same BUG sent in the first message :(.
Module:
ssize_t faulty_write(struct file *filp, const char __user *buf, size_t count,
loff_t *f_pos)
{
asm("int $25");
return count;
}
struct file_operations faulty_fops = {
.owner = THIS_MODULE,
.write = faulty_write,
};
/* [Normal char device initialization here] */
Thanks,
[Please use reply-to-all cause I wasn't CCed]
--
Ahmed S. Darwish
http://darwish.07.googlepages.com
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
