From: Michael Weissenbacher <webmaster@dermichi.com>
To: reiserfs-list@namesys.com
Cc: Alexander Zarochentsev <zam@namesys.com>
Subject: Re: reiser4 bug
Date: Tue, 11 Apr 2006 10:27:31 +0200 [thread overview]
Message-ID: <443B6873.8070506@dermichi.com> (raw)
In-Reply-To: <200604110954.29243.zam@namesys.com>
Hi,
> it is known problem. Fixed in 2.6.17-rc1-mm2
> (reiser4-have-get_exclusive_access-restart-transaction.patch).
as i've been burned by this bug, too i would suggest making a new patch
for 2.6.16 including
reiser4-have-get_exclusive_access-restart-transaction.patch
or at least put a warning there that the version is unstable. i'm sure
most people go straight for the vanilla kernel patch and don't bother
with mm-kernels. this puts reiser4 in a bad light imo.
kind regards,
Michael
--
/============================================================\
| Michael Weissenbacher <webmaster@dermichi.com> |
| http://www.dermichi.com/ |
| Email users are divided into two classes; |
| 1) Those who have effective spam-blocking |
| 2) Those who wish they did |
\============================================================/
next prev parent reply other threads:[~2006-04-11 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 5:28 reiser4 bug Matt Eaton
2006-04-11 5:54 ` Alexander Zarochentsev
2006-04-11 8:27 ` Michael Weissenbacher [this message]
2006-04-11 8:54 ` Avuton Olrich
2006-04-11 12:22 ` Alexander Zarochentsev
2006-04-11 6:35 ` Jake Maciejewski
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 8:58 Matt Eaton
2006-03-28 16:16 Reiser4 bug Alexander Gran
2006-03-28 16:37 ` Alexander Gran
2005-11-30 10:40 reiser4 bug Thomas Kuther
2005-02-27 19:34 Szabolcs Illes
2005-02-28 14:45 ` Alex Zarochentsev
2005-03-01 12:31 ` Szabolcs Illes
2005-03-04 13:48 ` Alex Zarochentsev
2005-03-04 14:38 ` Szabolcs Illes
2004-09-05 14:25 Scheduler experiences Markus Törnqvist
2004-09-05 15:55 ` Scheduler experiences (with Reiser4 bug report) mjt
2004-09-05 16:07 ` Reiser4 bug mjt
2004-09-05 16:07 ` Markus Törnqvist
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=443B6873.8070506@dermichi.com \
--to=webmaster@dermichi.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.com \
/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.