From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 14826] jdm-20002 reiserfs_xattr_get: Invalid hash for xattr
Date: Tue, 13 Apr 2010 15:41:25 GMT [thread overview]
Message-ID: <201004131541.o3DFfP7u002831@demeter.kernel.org> (raw)
In-Reply-To: <bug-14826-695@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14826
Greg Surbey <gregsurbey@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeffm@suse.com
--- Comment #4 from Greg Surbey <gregsurbey@hotmail.com> 2010-04-13 15:41:09 ---
Considering that this bug eventually leads to completely unrepairable
filesystem corruption, I strongly recommend that Linux revert to the old
reiserfs xattr pre-2.6.30 code for the time being. I realize that these code
improvements are a worthy goal, however this is supposed to be a stable kernel
release with a stable filesystem. Losing data is the worst thing that can
happen, but losing data silently/randomly is even worse. Unless this issue is
fixed today, this patch-set needs to go back to testing/development mode for
the time being.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-04-13 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14826-695@https.bugzilla.kernel.org/>
2010-04-12 18:52 ` [Bug 14826] jdm-20002 reiserfs_xattr_get: Invalid hash for xattr bugzilla-daemon
2010-04-13 8:55 ` bugzilla-daemon
2010-04-13 15:41 ` bugzilla-daemon [this message]
2010-04-13 18:59 ` bugzilla-daemon
2010-04-13 19:19 ` bugzilla-daemon
2010-05-11 9:50 ` bugzilla-daemon
2012-05-14 15:46 ` bugzilla-daemon
2012-05-14 15:47 ` bugzilla-daemon
2009-12-17 9:00 [Bug 14826] New: " bugzilla-daemon
2009-12-17 9:01 ` [Bug 14826] " bugzilla-daemon
2010-02-14 0:37 ` bugzilla-daemon
2010-03-18 13:22 ` bugzilla-daemon
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=201004131541.o3DFfP7u002831@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.