From: Paulo Alcantara <pc@manguebit.com>
To: Jeremy Allison <jra@samba.org>
Cc: David Howells <dhowells@redhat.com>,
Steve French <sfrench@samba.org>,
ronniesahlberg@gmail.com, aaptel@samba.org,
linux-cifs@vger.kernel.org
Subject: Re: cifs hardlink misbehaviour in generic/002?
Date: Fri, 01 Dec 2023 14:54:35 -0300 [thread overview]
Message-ID: <fc5847aac02cc745c46136a513898d1a@manguebit.com> (raw)
In-Reply-To: <ZWobTKPFwuY1GNgi@jeremy-HP-Z840-Workstation>
Jeremy Allison <jra@samba.org> writes:
> Looks like a ksmbd bug where it's not checking for multiple
> opens on close with DELETE_ON_CLOSE set, and just removing
> the file.
Interesting. Using 'nolease' mount option on the client make the issue
disappear.
next prev parent reply other threads:[~2023-12-01 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 16:15 cifs hardlink misbehaviour in generic/002? David Howells
2023-12-01 17:29 ` Paulo Alcantara
2023-12-01 17:42 ` David Howells
2023-12-01 17:43 ` Jeremy Allison
2023-12-01 17:54 ` Paulo Alcantara [this message]
2023-12-02 0:05 ` Namjae Jeon
2023-12-05 9:39 ` David Howells
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=fc5847aac02cc745c46136a513898d1a@manguebit.com \
--to=pc@manguebit.com \
--cc=aaptel@samba.org \
--cc=dhowells@redhat.com \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox