All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: dimas000@ya.ru
Cc: Reiserfs mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 for Linux-2.6.36
Date: Sun, 21 Nov 2010 19:08:59 +0100	[thread overview]
Message-ID: <4CE9603B.7050103@gmail.com> (raw)
In-Reply-To: <4CE93CEB.8050504@ya.ru>

dimas wrote:
> that sounds good! but as i remember, you've mentioned some issues about 2.6.35
> earlier, which were to be fixed. among them there was the troble with loop
> devices. how about this?

yes, this has been fixed in .36

>  and there was a mail here where author complained about
> problems after moving from 34 to 35. is 36 version more stable or it is better
> to still rely on 34.7, which works nice for me?
>   

I think that moving to .36 is a must, however I don't test
released stuff well enough, so, please keep a possibility
to roll back to previous stuff and report, if any problems.

> Edward Shishkin пишет:
>   
>> Changes since 2.6.35:
>>
>> . Fixed ->write_end() method: the old one didn't update i_size, and this
>>  resulted in empty files and "orphan" items. The problem took place only
>>  for splice users (loop devices, pipe2, etc).
>>
>> . Implemented ->sync_fs() method of super operations. Since introducing a
>>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>>  Now such sync is performed by reiser4_sync_fs().
>>
>> . Fixed an old bug which led to non-deletable directories.
>>
>> . Fixed an old bug in tail conversion, which led to data corruption when
>>  running in disk space pressure situations.
>>
>> Please, find at
>> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
>>     
>
>   

--
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

  parent reply	other threads:[~2010-11-21 18:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21  1:31 Reiser4 for Linux-2.6.36 Edward Shishkin
2010-11-21 11:17 ` Matt
2010-11-21 15:39 ` dimas
     [not found] ` <4CE93CEB.8050504@ya.ru>
2010-11-21 18:08   ` Edward Shishkin [this message]
2010-11-21 20:58     ` Юрий Заикин
2010-11-22  2:47       ` Edward Shishkin
2010-11-22  3:54         ` Edward Shishkin
2010-12-05 18:33           ` Юрий Заикин
2010-11-30 10:09 ` Simon
2010-11-30 11:38   ` Edward Shishkin
2010-11-30 16:00     ` Simon
2011-01-10 15:01       ` Simon
2011-01-10 15:28         ` Edward Shishkin
2011-01-10 17:14           ` Simon
2010-12-19  9:43 ` Serkan Kaba
2010-12-19 16:05   ` Edward Shishkin
2010-12-19 16:15     ` Serkan Kaba
2010-12-20 17:47       ` Serkan Kaba
2010-12-20 18:07         ` Edward Shishkin

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=4CE9603B.7050103@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=dimas000@ya.ru \
    --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.