From: Paulo Alcantara <pc@manguebit.org>
To: Ralph Boehme <slow@samba.org>, smfrench@gmail.com
Cc: Frank Sorenson <sorenson@redhat.com>,
David Howells <dhowells@redhat.com>,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH 1/3] smb: client: fix missing timestamp updates with O_TRUNC
Date: Mon, 06 Oct 2025 14:05:06 -0300 [thread overview]
Message-ID: <4c6d465a16a0b37f4601d418a11738d1@manguebit.org> (raw)
In-Reply-To: <1262e7b6-9086-404e-b9a5-e9c6208b8120@samba.org>
Ralph Boehme <slow@samba.org> writes:
> Fwiw, I have a patch in-flight that disables sticky write time behavour
> on POSIX handles in Samba.
Awesome! Thanks for letting me know.
prev parent reply other threads:[~2025-10-06 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 16:42 [PATCH 1/3] smb: client: fix missing timestamp updates with O_TRUNC Paulo Alcantara
2025-10-06 16:42 ` [PATCH 2/3] smb: client: fix missing timestamp updates after ftruncate(2) Paulo Alcantara
2025-10-06 16:42 ` [PATCH 3/3] smb: client: fix missing timestamp updates after utime(2) Paulo Alcantara
2025-10-06 17:02 ` [PATCH 1/3] smb: client: fix missing timestamp updates with O_TRUNC Ralph Boehme
2025-10-06 17:05 ` Paulo Alcantara [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:
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=4c6d465a16a0b37f4601d418a11738d1@manguebit.org \
--to=pc@manguebit.org \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=slow@samba.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).