On Thu, 28 Aug 2025 15:10:52 -0700
Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> And because the file pointer doesn't have any long-term meaning, it
> also means that you also can't make the mistake of thinking the hash
> has a long lifetime. With an inode pointer hash, you could easily have
> software bugs that end up not realizing that it's a temporary hash,
> and that the same inode *will* get two different hashes if the inode
> has been flushed from memory and then loaded anew due to memory
> pressure.
The hash value can actually last longer than the file pointer. Thus, if we
use the file pointer for the hash, then we could risk it getting freed and
then allocated again for different file. Then we get the same hash value
for two different paths.
What I'm looking at doing is using both the file pointer as well as its
path to make the hash:
struct jhash_key {
void *file;
struct path path;
};
u32 trace_file_cache_add(struct vm_area_struct *vma)
{
[..]
static u32 initval;
u32 hash;
if (!vma->vm_file)
return 0;
if (!initval)
get_random_bytes(&initval, sizeof(initval));
jkey.file = vma->vm_file;
jkey.path = vma->vm_file->f_path;
hash = jhash(&jkey, sizeof(jkey), initval);
if (!trace_file_cache_enabled())
return hash;
[ add the hash to the rhashtable and print if unique ]
Hopefully by using both the file pointer and its path to create the hash,
it will stay unique for some time.
-- Steve
