From: Alexander Beregalov <a.beregalov@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
linux-parisc@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
reiserfs-devel@vger.kernel.org
Subject: Re: 2.6.30-rc5: reiserfs is broken on parisc (bisected)
Date: Thu, 14 May 2009 15:04:13 +0400 [thread overview]
Message-ID: <a4423d670905140404n719f21f3jd841bf6fed3fd7be@mail.gmail.com> (raw)
In-Reply-To: <4A09AFD1.5090604@suse.com>
2009/5/12 Jeff Mahoney <jeffm@suse.com>:
> -----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.
prev parent reply other threads:[~2009-05-14 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 16:40 Alexander Beregalov
2009-05-12 17:20 ` Jeff Mahoney
2009-05-14 11:04 ` Alexander Beregalov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4423d670905140404n719f21f3jd841bf6fed3fd7be@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=jeffm@suse.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®