commit | acfa4380efe77e290d3a96b11cd4c9f24f4fbb18 | [log] [tgz] |
---|---|---|
author | Al Viro <viro@zeniv.linux.org.uk> | Thu Dec 04 10:06:33 2008 -0500 |
committer | Al Viro <viro@zeniv.linux.org.uk> | Mon Jan 05 11:54:28 2009 -0500 |
tree | d656232c7ef39c83681c2de4c8e28ba439242f66 | |
parent | 9742df331deb3fce95b321f38d4ea0c4e75edb63 [diff] |
inode->i_op is never NULL We used to have rather schizophrenic set of checks for NULL ->i_op even though it had been eliminated years ago. You'd need to go out of your way to set it to NULL explicitly _and_ a bunch of code would die on such inodes anyway. After killing two remaining places that still did that bogosity, all that crap can go away. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>