2009/5/12 Jeff Mahoney <jeffm@xxxxxxxx>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alexander Beregalov wrote: >> Hi >> >> ab17c4f02156c4f75d7fa43a5aa2a7f942d47201 is the first bad commit >> (reiserfs: fixup xattr_root caching) >> >> Kernel panics when init tries to remount rootfs (reiserfs) with >> read-write access. >> Read-only access works fine. >> >> No more messages on the screen before panic. >> >> Is it endianess related? > > No, not at all. There was a problem with the xattr code if the kernel > was built with xattrs disabled. It assumed that > REISERFS_SB(s)->xattr_root would be available, which isn't the case when > xattrs aren't enabled. Part of it has been cleaned up in -git1, and I've > sent Al some additional patches to fix the rest of it up. > > There's a thread called "reiserfs xattr fixups" that contains 4 patches. > The patch marked with * is the one I believe will fix your problem. > > - - reiserfs: cleanup ifdefs > - - reiserfs: deal with NULL xattr root w/ xattrs disabled * > - - reiserfs: fixup perms when xattrs are disabled > - - reiserfs: allow exposing privroot w/ xattrs enabled > It works! Thanks Jeff. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
