From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 197045] renameat2 rename_noreplace
Date: Tue, 24 Oct 2017 21:14:18 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: linux-ext4@kernel.org
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:49410 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1751494AbdJXVOT (ORCPT
);
Tue, 24 Oct 2017 17:14:19 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6007528A93
for ; Tue, 24 Oct 2017 21:14:19 +0000 (UTC)
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=197045
Theodore Tso (tytso@mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tytso@mit.edu
Resolution|--- |INVALID
--- Comment #11 from Theodore Tso (tytso@mit.edu) ---
I've confirmed that the test case works just fine on plain ext4, using the 4.13
based kernel. I've also confirmed that it works just fine if you use ext4
encryption. (I suggest that Ubuntu users file a feature request bug to Ubuntu
to ditch ecryptfs and switch to ext4 encryption.)
I can also confirm that ecryptfs != ext4, and that discussing this here has
approximately zero chance of it being noticed by the ecryptfs maintainer.
Since Tyler works at Canonical, filing a Launchpad bug is most likely to get
someone to look at it.
--
You are receiving this mail because:
You are watching the assignee of the bug.