Searched hist:fd2421f54423f307ecd31bdebdca6bc317e0c492 (Results 1 – 6 of 6) sorted by relevance
| /linux/fs/9p/ |
| H A D | cache.h | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|
| H A D | cache.c | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|
| H A D | v9fs.h | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|
| H A D | v9fs.c | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|
| H A D | vfs_inode_dotl.c | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|
| H A D | vfs_inode.c | diff fd2421f54423f307ecd31bdebdca6bc317e0c492 Mon Jul 11 18:40:59 CEST 2011 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> fs/9p: When doing inode lookup compare qid details and inode mode bits.
This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.
Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
|