| 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
| ||
|
Date: Fri, 21 Jul 2006 09:00:15 +1000 From: Nathan Scott <nathans@....com> To: Justin Piszcz <jpiszcz@...idpixels.com> Cc: Chris Wedgwood <cw@...f.org>, David Greaves <david@...eaves.com>, Kasper Sandberg <lkml@...anurb.dk>, Torsten Landschoff <torsten@...ian.org>, linux-kernel@...r.kernel.org, xfs@....sgi.com, ml@...og.se, radsaq@...il.com Subject: Re: FAQ updated (was Re: XFS breakage...) On Thu, Jul 20, 2006 at 06:55:51PM -0400, Justin Piszcz wrote: > Phase 6 - check inode connectivity... > - traversing filesystem starting at / ... > free block 16777216 for directory inode 2684356622 bad nused > free block 16777216 for directory inode 2147485710 bad nused > - traversal finished ... > ... > I applied the "one line fix" - I should be ok now? You have two corrupt directory inodes (caused by this bug, that is exactly the signature I'd expect - it was a nused field that was affected by the dodgey endian change). The two inodes need to be fixed - consult the FAQ for details. Once fixed, and with a patched kernel, you're set. cheers. -- Nathan - 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