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: <47A1E201.7070801@redhat.com> Date: Thu, 31 Jan 2008 08:58:09 -0600 From: Eric Sandeen <sandeen@...hat.com> To: Andreas Dilger <adilger@....com> CC: Andrew Morton <akpm@...ux-foundation.org>, linux-ext4@...r.kernel.org, Andreas Gruenbacher <agruen@...e.de>, bugme-daemon@...zilla.kernel.org, kmshanah@...b.org.au, "Theodore Ts'o" <tytso@....edu> Subject: Re: [Bugme-new] [Bug 9855] New: ext3 ACL corruption Andreas Dilger wrote: > On Jan 30, 2008 14:49 -0800, Andrew Morton wrote: >>> Problem Description: >>> Inode size: 256 > > This is a bit interesting, since it isn't very common to use large inodes. > I suspect this relates to the problem. I think it is somewhat common on samba servers, though. And it's the new default in the latest e2fsprogs... maybe something will shake out in the F9 development cycle. >>> These are production Samba servers making fairly extensive use of file and >>> directory ACLs. Thus far, I've only noticed the corruptions when it came time >>> to upgrade to a new kernel and reboot (and the boot scripts then run fsck). >>> Note that I've never noticed any issues at runtime because of this - only when >>> I later realised that ACLs had been removed from random files and/or >>> directories. >>> >>> I think I will implement some scripts to unmount and run fsck nightly from >>> cron, so I can at least detect the corruption a little earlier. If there is >>> some more helpful debugging output I can provide, please let me know. > > There is just such a script in the thread "forced fsck (again?)". Since you > are using LVs for the filesystem. Which is on the ext3-users list btw... > If you are able to reproduce this, could you please dump the inode and EA > block before fixing the problem. Do you need instructions on doing that? -Eric - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists