linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Baranger <nicolas.baranger@3xo.fr>
To: Paulo Alcantara <pc@manguebit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	hch@lst.de, David Howells <dhowells@redhat.com>,
	netfs@lists.linux.dev, linux-cifs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Steve French <smfrench@gmail.com>,
	Jeff Layton <jlayton@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [netfs/cifs - Linux 6.14] loop on file cat + file copy when files are on CIFS share
Date: Thu, 17 Apr 2025 12:10:20 +0200	[thread overview]
Message-ID: <e63e7c7ec32e3014eb758fd6f8679f93@3xo.fr> (raw)
In-Reply-To: <f12973bcf533a40ca7d7ed78846a0a10@manguebit.com>

Hi Paulo

Resending this mail with content-type: text, sorry !

Thanks again for answer and help, it's good to hear you're back to 
health.

> Thanks for the trace.  I was finally able to reproduce your issue and 
> will provide you with a fix soon.

Perfect... And thanks !

If you need more traces or details on (both?) issues :

- 1) infinite loop issue during 'cat' or 'copy' since Linux 6.14.0

- 2) (don't know if it's related) the very high number of several bytes 
TCP packets transmitted in SMB transaction (more than a hundred) for a 5 
bytes file transfert under Linux 6.13.8

Do not hesitate to ask, I would be happy to help.

Kind regards
Nicolas




Le 2025-04-15 20:28, Paulo Alcantara a écrit :

> Hi Nicolas,
> 
> Sorry for the delay as I've got busy with some downstream work.
> 
> Nicolas Baranger <nicolas.baranger@3xo.fr> writes:
> 
> I'll look into it as soon as I recover from my illness. Hope you're 
> doing better

I'm fully recovered now, thanks :-)

> I had to rollback to linux 6.13.8 to be able to use the SMB share and
> here is what I constat
> (don't know if it's a normal behavior but if yes, SMB seems to be a 
> very
> very unefficient protocol)
> 
> I think the issue can be buffer related:
> On Linux 6.13.8 the copy and cat of the 5 bytes 'toto' file containing
> only ascii string 'toto' is working fine but here is what I capture 
> with
> tcpdump during transfert of toto file:
> https://xba.soartist.net/t6.pcap
> 131 tcp packets to transfer a 5 byte file...
> Isn't there a problem ?
> Openning the pcap file with wireshark show a lot of lines:
> 25    0.005576    10.0.10.100    10.0.10.25    SMB2    1071    Read 
> Response, Error:
> STATUS_END_OF_FILE
> It seems that those lines appears after the 5 bytes 'toto' file had 
> been
> transferred, and it continue until the last ACK recieved

Thanks for the trace.  I was finally able to reproduce your issue and
will provide you with a fix soon.

  reply	other threads:[~2025-04-17 10:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 10:40 [netfs/cifs - Linux 6.14] loop on file cat + file copy when files are on CIFS share Nicolas Baranger
2025-03-27 11:15 ` Nicolas Baranger
2025-03-28 10:45   ` Christoph Hellwig
2025-04-04  8:50     ` Nicolas Baranger
2025-04-04 13:54       ` Paulo Alcantara
2025-04-10  8:43         ` Nicolas Baranger
2025-04-15 18:28           ` Paulo Alcantara
2025-04-17 10:10             ` Nicolas Baranger [this message]
2025-04-21 23:45               ` Paulo Alcantara
2025-04-23 16:28                 ` Nicolas Baranger
2025-04-24  7:40                   ` Nicolas Baranger
2025-04-24  8:39                     ` Nicolas Baranger
2025-04-24 14:25                       ` Paulo Alcantara
2025-05-06 22:53                         ` Paulo Alcantara
2025-05-07 15:58                           ` Nicolas Baranger
2025-04-24 13:58                     ` Steve French

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=e63e7c7ec32e3014eb758fd6f8679f93@3xo.fr \
    --to=nicolas.baranger@3xo.fr \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=jlayton@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=pc@manguebit.com \
    --cc=smfrench@gmail.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 NNTP newsgroup(s).