All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 197045] New: renameat2 rename_noreplace
Date: Tue, 26 Sep 2017 16:27:28 +0000	[thread overview]
Message-ID: <bug-197045-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 197045
           Summary: renameat2 rename_noreplace
           Product: File System
           Version: 2.5
    Kernel Version: 4.4.0, 4.11.0
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: martin@salbaba.co.at
        Regression: No

on ext4 renameat2 fails in conjunction with RENAME_NOREPLACE, if the target
file is not present

renameat2(AT_FDCWD, "rename-test-a", AT_FDCWD, "rename-test-c",
RENAME_NOREPLACE) = -1 EINVAL (Invalid argument)

if the target file is present, functionality is ok

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

             reply	other threads:[~2017-09-26 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 16:27 bugzilla-daemon [this message]
2017-09-26 16:42 ` [Bug 197045] renameat2 rename_noreplace 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
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@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.