Hello.
Tested kernels: 2.6.18, 2.6.22, 2.6.23-rc2
Steps to reproduce: Suppose that we have mounted some directory from nfs v3
server with default options. Also we have the two directories in this
mountpoint and each directory has hard linked file. Try to open those files
and write to one and read from another. Data will not be equal. (Testcase:
attached hardlink_test.c)
Analysis: Although these hard linked files have same nfs_fattr::fileid but
have different nfs_fh fhandle. In this case nfs_find_actor() function
(fs/nfs/inode.c) returns false during opening each file:
nfs_find_actor()
{
...
if (nfs_compare_fh(NFS_FH(inode), fh))
return 0;
...
}
Therefore for each of hard links new struct inode is allocated. It leads to
cache aliasing.
Please explain why nfs_find_actor() function compares file handles?
--
Thanks,
Vitaliy Gusev| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Eric Paris | [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| holzheu | Re: [RFC/PATCH] Documentation of kernel messages |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Alan Cox | Re: [BUG] New Kernel Bugs |
