[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A09AFD1.5090604@suse.com>
Date: Tue, 12 May 2009 13:20:17 -0400
From: Jeff Mahoney <jeffm@...e.com>
To: Alexander Beregalov <a.beregalov@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
linux-parisc@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>,
reiserfs-devel@...r.kernel.org
Subject: Re: 2.6.30-rc5: reiserfs is broken on parisc (bisected)
-----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
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkoJr9EACgkQLPWxlyuTD7JbfACfSV+WiMxReRCr/YRDT8IBf7M8
jVkAn3fhf3R1i5cyi/YJ+vtO/WTd6Lre
=90Xq
-----END PGP SIGNATURE-----
--
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