[LART] inode mismanagement in hugetlb code

From: Alexander Viro (viro@math.psu.edu)
Date: Thu Oct 10 2002 - 14:00:37 EST


[A discussion of the meanings of the terms "MUST", "SHOULD", and "MAY" appears
in RFC-1123; the terms "MUST NOT" and "SHOULD NOT" are logical extensions of
this usage]

        a) inodes MUST have an address of valid struct super_block in their
->i_sb. Had been discussed quite a few times already.

        b) inodes MUST NOT be allocated by code that isn't called from
alloc_inode().

        c) inodes SHOULD NOT be kept around for noticable intervals without
a dentry pointing to them.

        d) people who choose variable names like htlbpagek SHOULD be sent to
produce a street map of R'Lyeh. On site.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:38 EST