From: Edward Shishkin <edward@namesys.com>
To: Ignatich <ignatich@gmail.com>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
Jonathan Briggs <jbriggs@esoft.com>
Subject: Re: [Fwd: reiser4 bugs in 2.6.21-rc4]
Date: Wed, 28 Mar 2007 00:14:31 +0400 [thread overview]
Message-ID: <46097B27.6090606@namesys.com> (raw)
In-Reply-To: <460974EE.8080006@gmail.com>
Ignatich wrote:
>
>
> ------------------------------------------------------------------------
>
> Subject:
> reiser4 bugs in 2.6.21-rc4
> From:
> Ignatich <ignatich@gmail.com>
> Date:
> Tue, 27 Mar 2007 23:29:18 +0400
> To:
> linux-kernel@vger.kernel.org
>
> To:
> linux-kernel@vger.kernel.org
>
> Message-ID:
> <4609708E.5090908@gmail.com>
> User-Agent:
> Thunderbird 1.5.0.10 (Windows/20070221)
> MIME-Version:
> 1.0
> Content-Type:
> text/plain; charset=windows-1251; format=flowed
> Content-Transfer-Encoding:
> 7bit
>
>
> There are two bugs I found in current -mm reiser4 code.
>
> 1. Some files seem to be zeroed out randomly. Usually it's
> /lib/security/pam_limits.so and /lib/security/pam_deny.so. As
> fsck.reiser4 didn't find anything wrong I decided to create clean
> installation in vmware and see if this bug appears on newly formatted
> partition. It did.
>
> 2. Sometimes I get oppses in reiser4_do_readpage_extent. Assert codes
> are vs-1426 and nikita-2688. A patch was posted on namesys list to
> address this problem, but it didn't help.
>
> Kernel: 2.6.21-rc4 with manually applied reiser4 patches from -mm.
> Arch: x86-64
>
We are working on this.
Thanks for reports,
Edward.
parent reply other threads:[~2007-03-27 20:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <460974EE.8080006@gmail.com>]
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=46097B27.6090606@namesys.com \
--to=edward@namesys.com \
--cc=ignatich@gmail.com \
--cc=jbriggs@esoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox