> Speaking of obvious holes, what is > /* Setting file->private_data can't race with other mount() > instances, since BKL is held for ->get_sb() */ > if (file->private_data) > return -EINVAL; > doing, seeing that the next thing you do is GFP_KERNEL allocations, which > would kill all hope to use BKL-based protection here? Why? I didn't know BKL is incompatible with allocations. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
