[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-197045-13602-0WYLoK3uXE@https.bugzilla.kernel.org/>
Date: Tue, 24 Oct 2017 12:29:42 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...nel.org
Subject: [Bug 197045] renameat2 rename_noreplace
https://bugzilla.kernel.org/show_bug.cgi?id=197045
--- Comment #3 from Elvis Stansvik (elvstone@...il.com) ---
I'm hit by this on 4.10 a well (the default kernel on Ubuntu 16.04).
I attached a full test case showing.
Example run:
> [estan@...ton renameat2tc]$ gcc renameat2.c
> [estan@...ton renameat2tc]$ touch foo
> [estan@...ton renameat2tc]$ ./a.out foo bar
> Invalid argument
> [estan@...ton renameat2tc]$ uname -a
> Linux newton 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:59 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
> [estan@...ton renameat2tc]$ mount | grep " / "
> /dev/sda1 on / type ext4 (rw,noatime,discard,errors=remount-ro,data=ordered)
The reason I discovered it was that Qt recently started using this syscall,
which in turn made Qt Creator (a Qt application) fail to write its config
files.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists