From: Arjan van de Ven lockdep added a WARN_ON in block_dev.c that not only triggers on my raid system, it seems to be entirely wrong in the first place. Just removing it entirely seems the most sensible thing at this point. Signed-off-by: Arjan van de Ven Cc: Ingo Molnar Signed-off-by: Andrew Morton --- fs/block_dev.c | 4 ---- 1 file changed, 4 deletions(-) diff -puN fs/block_dev.c~lock-validator-special-locking-bdev-fix fs/block_dev.c --- devel/fs/block_dev.c~lock-validator-special-locking-bdev-fix 2006-06-09 15:18:40.000000000 -0700 +++ devel-akpm/fs/block_dev.c 2006-06-09 15:18:40.000000000 -0700 @@ -937,10 +937,6 @@ do_open(struct block_device *bdev, struc struct block_device *whole; whole = bdget_disk(disk, 0); ret = -ENOMEM; - /* - * We must not recurse deeper than 1: - */ - WARN_ON(subtype != 0); if (!whole) goto out_first; ret = blkdev_get_whole(whole, file->f_mode, file->f_flags); _