From: Edward Shishkin <edward@namesys.com>
To: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Cc: Edward Shishkin <edward.shishkin@gmail.com>
Subject: Reiser4 for 2.6.22
Date: Sat, 21 Jul 2007 23:19:18 +0400 [thread overview]
Message-ID: <46A25C36.1060005@namesys.com> (raw)
Hello everyone.
The corporative Namesys server doesn't work,
and I don't know how much time it will be in such
state. So I have put the patch in this place:
http://chichkin_i.zelnet.ru/namesys/index.html
<http://chichkin_i.zelnet.ru/namesys/index.html>
The list of changes since reiser4-for-2.6.21:
1) Common changes:
. Reduce number of typedefs from 289 to 248
. Remove unused file plugin/file/invert.c
2) unix-file plugin fixups:
. Fixed bug in extent2tail conversion.
Bug description:
when converting partially converted file
(with flag REISER4_PART_MIXED installed)
reiser4_cut_tree() starts to cut old metatada
from wrong offset. Result is data corruption
when booting after system crash, power loss,
etc.
. Update hint when reading tails (failed assertion
nikita-19891 reported by Jake Maciejewski,
Ingo Bormuth)
. Protect page (via incrementing page count) from
being reclaimed when looking for extent pointer
in unix-file specific readpages filler (oops reported
by Zan Lynx).
3) cryptcompress file plugin fixups:
. Fix a race (reproducible by fsx + sync(1))
between checkin page cluster operations:
serialize them via special per-inode checkin_mutex
(usual i_mutex is not suitable for this purpose,
as ->writepages() also calls checkin_page_cluster();
. Add comments for checkin/checkout technique for
synchronization of primary and secondary caches
with proof of correctness;
. Fix missed right neighbor when updating disk
clusters by handle_pos_on_leaf() during squalloc
(should use upper levels to get expected non-connected
neighbor);
. Resolve a race between read and truncate (when read
finds partially truncated and, hence, unrecoverable
disk cluster) via keeping a track of leftmost
truncated disk clusters in cryptcompress-specific
part of inode;
. Update comments;
. Rename badly sounding function names;
. Fix coding style;
Thanks,
Edward.
next reply other threads:[~2007-07-21 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 19:19 Edward Shishkin [this message]
2007-07-21 19:59 ` Reiser4 for 2.6.22 timotheus
2007-07-21 23:07 ` Edward Shishkin
2007-07-23 6:45 ` Raymond A. Meijer
2007-07-23 7:03 ` Raymond A. Meijer
[not found] ` <20070726195357.GA31116@izvekov.dyndns.org>
2007-07-26 21:49 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 23:35 Mat
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=46A25C36.1060005@namesys.com \
--to=edward@namesys.com \
--cc=edward.shishkin@gmail.com \
--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.