From: "Lukáš Czerner" <lczerner@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz, stable@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix punch hole on files with indirect mapping
Date: Fri, 27 Jun 2014 12:58:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1406271257250.2349@localhost.localdomain> (raw)
In-Reply-To: <20140627013329.GE6826@thunk.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1047 bytes --]
On Thu, 26 Jun 2014, Theodore Ts'o wrote:
> Date: Thu, 26 Jun 2014 21:33:29 -0400
> From: Theodore Ts'o <tytso@mit.edu>
> To: Lukáš Czerner <lczerner@redhat.com>
> Cc: linux-ext4@vger.kernel.org, jack@suse.cz, stable@vger.kernel.org
> Subject: Re: [PATCH] ext4: Fix punch hole on files with indirect mapping
>
> On Thu, Jun 26, 2014 at 06:28:57PM +0200, Lukáš Czerner wrote:
> >
> > It does. But this is not exactly a critical bug and it has been
> > there since the introduction of punch hole for indirect file. But I
> > guess it's better to fix it sooner rather than later, so I am fine
> > with this.
>
> One of the reasons why I want to get this fixed sooner rather than
> later is that even when testing a stock ext4 file system, fsstress can
> potentially create indirect mapped files that could then get punched.
> So I wonder if bug might be responsible for some of the very random
> failures that I've been seeing in my testing...
>
> - Ted
Fair enough, we can wait with my patch for the next merge window.
Thanks!
-Lukas
prev parent reply other threads:[~2014-06-27 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 15:37 [PATCH] ext4: Fix punch hole on files with indirect mapping Lukas Czerner
2014-06-19 17:45 ` Jan Kara
2014-06-20 11:28 ` Lukáš Czerner
2014-06-23 9:40 ` Lukáš Czerner
2014-06-26 16:24 ` Theodore Ts'o
2014-06-26 16:28 ` Lukáš Czerner
2014-06-26 16:30 ` Lukáš Czerner
2014-06-27 1:33 ` Theodore Ts'o
2014-06-27 10:58 ` Lukáš Czerner [this message]
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=alpine.LFD.2.00.1406271257250.2349@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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