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: Wed, 07 May 2025 17:58:58 +0200 [thread overview]
Message-ID: <4367e54becaf348ac6c18e0b298dcd7e@3xo.fr> (raw)
In-Reply-To: <df978e3da9bec1a5e040448f6341b646@manguebit.com>
Hi Paulo
I'm testing this branch and going back with results
Thanks again !
Nicolas
Le 2025-05-07 00:53, Paulo Alcantara a écrit :
> Hi Nicolas,
>
> Could you try my cifs.dio branch [1] which contains the following fixes
>
> afea8b581c75 ("netfs: Fix wait/wake to be consistent about the
> waitqueue used")
> ae9f3deaa17a ("netfs: Fix the request's work item to not require a
> ref")
> b2a47dc3ead6 ("netfs: Fix setting of transferred bytes with short DIO
> reads")
> c59f7c9661b9 ("smb: client: ensure aligned IO sizes")
>
> Let me know if you find any issues with it. Thanks.
>
> [1] https://git.manguebit.com/linux.git
next prev parent reply other threads:[~2025-05-07 16:05 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
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 [this message]
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=4367e54becaf348ac6c18e0b298dcd7e@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 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.