From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 197045] renameat2 rename_noreplace
Date: Tue, 24 Oct 2017 21:14:18 +0000 [thread overview]
Message-ID: <bug-197045-13602-syo42gdG4M@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197045-13602@https.bugzilla.kernel.org/>
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.
next prev parent reply other threads:[~2017-10-24 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 16:27 [Bug 197045] New: renameat2 rename_noreplace bugzilla-daemon
2017-09-26 16:42 ` [Bug 197045] " bugzilla-daemon
2017-10-24 12:28 ` bugzilla-daemon
2017-10-24 12:29 ` bugzilla-daemon
2017-10-24 17:41 ` bugzilla-daemon
2017-10-24 19:22 ` bugzilla-daemon
2017-10-24 19:31 ` bugzilla-daemon
2017-10-24 19:35 ` bugzilla-daemon
2017-10-24 19:41 ` bugzilla-daemon
2017-10-24 20:25 ` bugzilla-daemon
2017-10-24 21:03 ` bugzilla-daemon
2017-10-24 21:14 ` bugzilla-daemon [this message]
2017-10-24 21:35 ` bugzilla-daemon
2017-10-24 21:42 ` bugzilla-daemon
2017-10-25 8:59 ` bugzilla-daemon
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-197045-13602-syo42gdG4M@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 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).