Repeated oopses with inode == 0xffffffff in 2.6.23

[Chuck Ebbert]

What does it mean when a pointer to an inode has a value of -1?

https://bugzilla.redhat.com/show_bug.cgi?id=334181


/usr/src/debug/kernel-2.6.22/linux-2.6.22.x86_64/block/ll_rw_blk.c:3139
ffffffff8110854e:       48 8b 45 10             mov    0x10(%rbp),%rax
ffffffff81108552:       48 8b 40 08             mov    0x8(%rax),%rax
ffffffff81108556:       48 8b 40 68             mov    0x68(%rax),%rax

       maxsector = bio->bi_bdev->bd_inode->i_size >> 9;

bd_inode == -1

-----------

rw_verify_area+0x24/0x7e

inode == -1 again


------- Additional Comments From cebbert@xxxxxxxxxx  2007-11-14 18:39 EST -------
fs/dnotify.c:46:

        inode = filp->f_path.dentry->d_inode;
===>    if (!S_ISDIR(inode->i_mode))
                return;

inode is -1 again


-
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/