All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194739] fallocate --collapse-range causes temporal data corruption on fragmented file
Date: Wed, 15 Mar 2017 17:48:30 +0000	[thread overview]
Message-ID: <bug-194739-13602-8sHD4Telsc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194739-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=194739

Ivan Kalvachev (iive@yahoo.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #1 from Ivan Kalvachev (iive@yahoo.com) ---
With kernel-4.10.2 I cannot reproduce the bug anymore.

The following commit looks like it might be the one fixing the issue:
---
commit 011fe6ade610c2ca5a609c83c509f1fc8e4c8b7f
Author: Roman Pen <roman.penyaev@profitbricks.com>
Date:   Sun Jan 8 21:00:35 2017 -0500

    ext4: do not polute the extents cache while shifting extents

    commit 03e916fa8b5577d85471452a3d0c5738aa658dae upstream.

    Inside ext4_ext_shift_extents() function ext4_find_extent() is called
    without EXT4_EX_NOCACHE flag, which should prevent cache population.

    This leads to oudated offsets in the extents tree and wrong blocks
    afterwards.

    Patch fixes the problem providing EXT4_EX_NOCACHE flag for each
    ext4_find_extents() call inside ext4_ext_shift_extents function.

    Fixes: 331573febb6a2
---

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2017-03-15 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  0:00 [Bug 194739] New: fallocate --collapse-range causes temporal data corruption on fragmented file bugzilla-daemon
2017-03-15 17:48 ` bugzilla-daemon [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=bug-194739-13602-8sHD4Telsc@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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.