From: Paulo Alcantara <pc@manguebit.org>
To: Ralph Boehme <slow@samba.org>, Steve French <smfrench@gmail.com>
Cc: Jean-Baptiste Denis <jbdenis@pasteur.fr>,
Frank Sorenson <sorenson@redhat.com>,
Olga Kornievskaia <okorniev@redhat.com>,
Benjamin Coddington <bcodding@redhat.com>,
Scott Mayhew <smayhew@redhat.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH v2] smb: client: fix data loss due to broken rename(2)
Date: Tue, 02 Sep 2025 16:39:12 -0300 [thread overview]
Message-ID: <b29ed180e00cf6197644e54d944c59fc@manguebit.org> (raw)
In-Reply-To: <e66bfd26-9766-4075-bb8e-89df33e88e59@samba.org>
Ralph Boehme <slow@samba.org> writes:
> Likely? How? Does a Windows client also do this stuff when the rename
> destination is open? All this additionaly complexity is only waiting for
> bugs to happen and now that we have POSIX Extensions back we should
> phase out this crap.
Claiming POSIX support and being unable to rename open files, that would
be even worse, no?
next prev parent reply other threads:[~2025-09-02 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 16:54 [PATCH v2] smb: client: fix data loss due to broken rename(2) Paulo Alcantara
2025-09-02 18:57 ` Ralph Boehme
[not found] ` <CAH2r5mvqJXfgQwKLSWrfBDw8Rc88ys8a_cWB5DtD19HSDmFn5w@mail.gmail.com>
2025-09-02 19:05 ` Ralph Boehme
2025-09-02 19:39 ` Paulo Alcantara [this message]
2025-09-03 15:48 ` Ralph Boehme
2025-09-03 16:19 ` Paulo Alcantara
2025-09-04 6:04 ` Ralph Boehme
2025-09-02 19:09 ` Paulo Alcantara
2025-09-03 16:10 ` Ralph Boehme
2025-09-03 18:45 ` Paulo Alcantara
2025-09-03 19:55 ` ronnie sahlberg
2025-09-03 20:10 ` ronnie sahlberg
2025-09-03 20:28 ` Paulo Alcantara
2025-09-03 20:44 ` ronnie sahlberg
2025-09-03 20:55 ` Paulo Alcantara
2025-09-03 20:18 ` Paulo Alcantara
2025-09-03 19:13 ` Paulo Alcantara
[not found] ` <notmuch-sha1-4fd369d43684b0739d61e9e931e63ca8c7e2a82c>
2025-09-02 19:10 ` Paulo Alcantara
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=b29ed180e00cf6197644e54d944c59fc@manguebit.org \
--to=pc@manguebit.org \
--cc=bcodding@redhat.com \
--cc=jbdenis@pasteur.fr \
--cc=linux-cifs@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=slow@samba.org \
--cc=smayhew@redhat.com \
--cc=smfrench@gmail.com \
--cc=sorenson@redhat.com \
/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.