From: Dominique Martinet <asmadeus@codewreck.org>
To: Steve French <smfrench@gmail.com>
Cc: Forest <forestix@nom.one>, David Howells <dhowells@redhat.com>,
Steve French <sfrench@samba.org>,
Shyam Prasad N <nspmangalore@gmail.com>,
Rohith Surabattula <rohiths.msft@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
linux-cifs@vger.kernel.org, netfs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
regressions@lists.linux.dev,
Christian Brauner <brauner@kernel.org>
Subject: Re: [REGRESSION] cifs: Subreq overread in dmesg, invalid argument & no data available in apps
Date: Tue, 27 Aug 2024 13:38:02 +0900 [thread overview]
Message-ID: <Zs1YKh8H0dEX126X@codewreck.org> (raw)
In-Reply-To: <CAH2r5mt99dz9AjEYvMpBUXoNLePdbK5p0OuH0Lq1tf4m+ExLpw@mail.gmail.com>
Steve French wrote on Mon, Aug 26, 2024 at 11:27:33PM -0500:
> I have also confirmed your theory that the regressions (there are
> multiple) were likely caused by the netfs change added between
> 6.11-rc3 and 6.11-rc4:
> " 9p: Fix DIO read through netfs"
>
> But reverting the cifs.ko part of that patch alters the error but does
> not completely fix the problem, so the netfs change is also related
David sent a bunch of cifs fixes including this patch:
https://lore.kernel.org/r/20240823200819.532106-8-dhowells@redhat.com
"netfs, cifs: Fix handling of short DIO read"
I don't have any samba server around to try myself, did you have a
chance to have a look?
That "9p" commit touches all netfs filesystems and definitely shouldn't
have been labeled 9p (even if it does fix a 9p regression from an
earlier netfs commit...), and this all feels a bit like falling forward
but hopefully we can get this all fixed by the time 6.11 is ready...
--
Dominique
next prev parent reply other threads:[~2024-08-27 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 23:26 Forest
2024-08-27 3:32 ` Steve French
2024-08-27 4:27 ` Steve French
2024-08-27 4:38 ` Dominique Martinet [this message]
2024-08-27 5:02 ` Steve French
2024-08-27 18:15 ` Forest
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=Zs1YKh8H0dEX126X@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=forestix@nom.one \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netfs@lists.linux.dev \
--cc=nspmangalore@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=rohiths.msft@gmail.com \
--cc=sfrench@samba.org \
--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