From: Edward Shishkin <edward.shishkin@gmail.com>
To: ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Cc: "Ivan Shapovalov" <intelfx100@gmail.com>,
"Marcin Baczyński" <marbacz@gmail.com>
Subject: Reiser4 for Linux-3.5
Date: Sat, 08 Sep 2012 22:51:26 +0200 [thread overview]
Message-ID: <504BAFCE.7@gmail.com> (raw)
Hello everyone.
Please, find at
http://sourceforge.net/projects/reiser4/files/reiser4-for-linux-3.x/
Changes since 2.6.39:
Marcin Baczyński :
. Port reiser4-for-2.6.39 to 3.2
Ivan Shapovalov :
. Adjust reiser4-for-3.2 to 3.5;
. Use umode_t as file mode type;
. show_options() takes dentry;
. Use d_make_root() instead of d_alloc_root();
. Use clear_inode() instead of end_writeback();
. Adjust to changes in encode_fh() API;
. lock ->i_mutex in reiser4_sync_file_common();
. Introduce INODE_{INC,DROP,CLEAR,SET}_NLINK macros,
which use library function for i_nlink manipulations;
. Do not make reiser4_permission_common() bail out on
rcu-walk;
. Don't clear nlink in reiser4's do_create_vfs_child().
Edward Shishkin :
. Reserve space in reiser4_write_begin() properly.
Fix deadlock (reiser4 lock ordering violation):
release page lock in reiser4_dirty_inode() before
acquiring a longterm lock;
Current status
The bug in the balancing primitive INSERT_FLOW (which
led to inconsistent key ordering) is not yet fixed.
So the following features can lead to data corruption:
. tail packing in the default file plugin;
. transparent compression.
Fsck will fix everything, however, it can be rather
annoying to check production systems frequently..
Thanks,
Edward.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2012-09-08 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=504BAFCE.7@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx100@gmail.com \
--cc=marbacz@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.