| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <e38d12ff0811210859r7103c20nb1bf9c6e5025d1c5@mail.gmail.com> Date: Fri, 21 Nov 2008 11:59:32 -0500 From: "Andrey Vul" <andrey.vul@...il.com> To: linux-kernel <linux-kernel@...r.kernel.org> Subject: Bad inodes and ESTALE Why do files/directories located on unreadable inodes cause ESTALE when trying to access ( open()) or modify (unlink()) them? I know it's caused by a bad inode because fsck -f fixes all of the problems. -- Andrey Vul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists