[BUG?] dev_close() is called with locks held

From: Kirill Korotaev
Date: Fri Nov 19 2004 - 04:02:17 EST


Hello,

looks like a bug in 2.4/2.6 kernels:

1. dev_close() function is blocking. it calls schedule() inside and calls blocking dev_deactivate() function.

2. But... call chain
dev_ioctl() -> dev_ifsioc() -> dev_change_flags() calls dev_close() under read_lock(&dev_base_lock)...

Bug?

Kirill

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