reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: [RFC] [PATCHv2 0/3] reiser4: block deallocation fixes.
Date: Mon, 08 Sep 2014 22:19:35 +0200	[thread overview]
Message-ID: <540E0F57.5090503@gmail.com> (raw)
In-Reply-To: <1965626.b15caRcJVX@intelfx-laptop>


On 09/08/2014 09:52 PM, Ivan Shapovalov wrote:
> On Monday 08 September 2014 at 21:03:17, Edward Shishkin wrote:	
>> Ok, I'll include this to the 3.15.2-reiser4-basic-discard-support.patch
> Good, at least this is done...
>
>> As to 3.16: unfortunately the ancient bug, which leads to non-deleted
>> directories raised the head in 3.16. I don't want to release buggy stuff.
>> So let's work around the stable 3.15 for now..
> Uhm, what relation does that bug have to 3.16? Does it manifest itself more often?


I can reproduce it in 3.10, 3.16.
I can not in 3.11 - 3.15..

  reply	other threads:[~2014-09-08 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 18:43 [RFC] [PATCHv2 0/3] reiser4: block deallocation fixes Ivan Shapovalov
2014-09-08 18:43 ` [RFC] [PATCHv2 1/3] reiser4: deferred (BA_DEFER) deallocations do not make use of target stage Ivan Shapovalov
2014-09-08 18:43 ` [RFC] [PATCHv2 2/3] reiser4: mark final deallocations in wandering log code as deferred Ivan Shapovalov
2014-09-08 18:43 ` [RFC] [PATCHv2 3/3] reiser4: block_alloc: get rid of discard-related hack in reiser4_dealloc_blocks() Ivan Shapovalov
2014-09-08 19:03 ` [RFC] [PATCHv2 0/3] reiser4: block deallocation fixes Edward Shishkin
2014-09-08 19:52   ` Ivan Shapovalov
2014-09-08 20:19     ` Edward Shishkin [this message]
2014-09-08 21:13       ` Ivan Shapovalov

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=540E0F57.5090503@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=intelfx100@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 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).