* Reiser4 for Linux-3.5
@ 2012-09-08 20:51 Edward Shishkin
0 siblings, 0 replies; only message in thread
From: Edward Shishkin @ 2012-09-08 20:51 UTC (permalink / raw)
To: ReiserFS Development List; +Cc: Ivan Shapovalov, Marcin Baczyński
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-08 20:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-08 20:51 Reiser4 for Linux-3.5 Edward Shishkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).