diff options
| author | Jeff Layton <jlayton@redhat.com> | 2010-08-02 17:43:54 -0400 |
|---|---|---|
| committer | Steve French <sfrench@us.ibm.com> | 2010-08-05 17:17:50 +0000 |
| commit | 5acfec2502cf60a91dc1959e476b588ecb3a1b8a (patch) | |
| tree | 52742d8c6643d534b37d60aad918cbe38c695665 /net/dns_resolver/Makefile | |
| parent | 67b7626a0512d12e34b38ff45e32c693cf9c79a1 (diff) | |
| download | kernel_samsung_smdk4412-5acfec2502cf60a91dc1959e476b588ecb3a1b8a.zip kernel_samsung_smdk4412-5acfec2502cf60a91dc1959e476b588ecb3a1b8a.tar.gz kernel_samsung_smdk4412-5acfec2502cf60a91dc1959e476b588ecb3a1b8a.tar.bz2 | |
cifs: reduce false positives with inode aliasing serverino autodisable
It turns out that not all directory inodes with dentries on the
i_dentry list are unusable here. We only consider them unusable if they
are still hashed or if they have a root dentry attached.
Full disclosure -- this check is inherently racy. There's nothing that
stops someone from slapping a new dentry onto this inode just after
this check, or hashing an existing one that's already attached. So,
this is really a "best effort" thing to work around misbehaving servers.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'net/dns_resolver/Makefile')
0 files changed, 0 insertions, 0 deletions