archive mirror
 help / color / mirror / Atom feed
From: Steve French <>
To: Jan Melcher <>
Cc: CIFS <>
Subject: Re: Question regarding the patch "cifs: Fix the target file was deleted when rename failed."
Date: Wed, 5 May 2021 08:28:06 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Your points are good ones - and it is worth revisiting the
'silly-rename' approach to a workaround (and others if people have
ideas here). Although this is solved with the SMB3.1.1 POSIX
Extensions (more exact semantics for the rename and delete of open
files) the majority of servers don't support that yet so this is
important to follow up more.

Would be interested in opinion of others on these patches - and it
might help for your example if you took your example above and put it
in a simple script (might save a few minutes of time for others
wanting to experiment with this scenario).

On Wed, May 5, 2021 at 6:10 AM Jan Melcher <> wrote:
> I hope this is the right place for me to start a discussion regarding
> a problem in the cifs file system.
> I'm experiencing the problem the patch "cifs: Fix the target file was
> deleted when rename failed."
> (
> was trying to solve. It was further described in the samba-technical
> mailing list (
> The patch was eventually reverted
> (
> Before I found the patch and the mailing list entry, I produced the
> problem with the following sequence:
> $ exec 20>file # open file and leave file descriptor open
> $ touch file.lock
> $ mv file.lock file
> mv: cannot move 'file.lock' to 'file': Permission denied
> $ ls -la
> total 16
> drwxr-xr-x 2 2000 2000     0 May  4 12:17 .
> drwxr-xr-x 2 2000 2000 16384 May  4 12:17 ..
> -rwxr-xr-x 1 2000 2000     0 May  4 12:17 file.lock
> In other words, renaming a file onto an existing file that has an open
> file descriptor effectively deletes that original target file. This
> happens both with samba and with a Windows server. I thzink this
> command sequence seems is quite common because that's the way many
> applications do file locking on posix file systems. In our case, the
> problem corrupted Git repositories multiple times because of packfile
> indices getting deleted.
> The patch I linked would have reduced the problem from a corruption to
> a mere failed operation (the unlink-then-rename strategy is the last
> resort at that place; if it is skipped, the rename fails).
> Digging through the cifs history, I found this patch
> (
> from 2008: "cifs: make cifs_rename handle -EACCES errors". It tried to
> rename the target file to a random name (a "silly rename" I guess) and
> also marked it for deletion, then tried the actual rename operation.
> In my understanding, this solution should solve the mentioned problem
> because renames are still allowed for files that have open file
> handles. (Of course with the problem that for a short time, the target
> file does not exist at all, but this problem also exists today).
> The patch has been reverted shortly after
> (
> because it would cause problems with servers that do not support busy
> file renames. Maybe the situation changed since 2008 and there are
> less servers that do not support busy file renames (my Windows machine
> supports it), or we could find a way to re-implement the patch for
> servers that do support busy file renames. The logic to handle a file
> handle on the source file already tries to to a busy-file-rename by
> the way.
> These are just my thoughts after two days of digging into the problems
> and never having seen the cifs code before, so please forgive me if
> I'm just talking nonsense. But it would be great to hear what you
> think about this.
> Jan



      reply	other threads:[~2021-05-05 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 11:09 Question regarding the patch "cifs: Fix the target file was deleted when rename failed." Jan Melcher
2021-05-05 13:28 ` Steve French [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).