* Chuck Ebbert <cebbert@xxxxxxxxxx> wrote: > I get the feeling that some of the bugs we are seeing is because we > have enabled CONFIG_PREEMPT_BKL. I remember looking at the code when > it came out and thinking it was too scary to enable, so I never did in > my own vanilla kernels. yes, we should keep it enabled - it's the default upstream and we havent had PREEMPT_BKL related bugs for a really long time. in fact i had more !PREEMPT_BKL bugs than PREEMPT_BKL bugs. (BKL spinlock recursion for example) Ingo