From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 197045] renameat2 rename_noreplace
Date: Tue, 24 Oct 2017 12:29:42 +0000 [thread overview]
Message-ID: <bug-197045-13602-0WYLoK3uXE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197045-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197045
--- Comment #3 from Elvis Stansvik (elvstone@gmail.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@newton renameat2tc]$ gcc renameat2.c
> [estan@newton renameat2tc]$ touch foo
> [estan@newton renameat2tc]$ ./a.out foo bar
> Invalid argument
> [estan@newton 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@newton 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.
next prev parent reply other threads:[~2017-10-24 12:29 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 [this message]
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
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-0WYLoK3uXE@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.