From: matoro <matoro_mailinglist_kernel@matoro.tk>
To: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Cc: Steve French <smfrench@gmail.com>,
Linux Cifs <linux-cifs@vger.kernel.org>,
Bruno Haible <bruno@clisp.org>
Subject: Re: CIFS lockup regression on SMB1 in 6.10
Date: Tue, 03 Sep 2024 00:55:28 -0400 [thread overview]
Message-ID: <2925a37f946d1b96a7251f7be72ba341@matoro.tk> (raw)
In-Reply-To: <90134f35-acb3-4124-b172-2de6d70dd0b4@moonlit-rail.com>
On 2024-08-23 16:51, Kris Karas (Bug Reporting) wrote:
> Steve French wrote:
>> On Aug 20 Kris Karas wrote:
>>> Don't remember just when this started, maybe around
>>> 6.10.3 or 6.10.4? Can bisect if need be.
>
> I neglected to ask if any of the devs on Linux-CIFS know the culprit and
> thus what to fix, or whether somebody would like me to bisect? Happy to do
> so. Let me know.
>
>> Smb311 Linux extensions work to ksmbd but for those extensions to samba
>> there is a server bug with qfsinfo but patch is available for that
>
> Super! I'm glad to hear it. I've been stubbornly stuck using vers=1.0
> because I know of no other alternative. I have heard of unofficial patches
> to Samba going back at least a couple years, and have been patiently
> awaiting official blessing; I'm sadly ignorant of the reasons for rebuff.
>
> Kris
Kris, a bisesct attempt would be immensely helpful. My attempt failed as
there were other unrelated problems in the commit range which caused my test
reproducer (compiling python) to fail, but your reproducer seems much more
reliable (reading images). Could you please take a crack at it and see what
turns up? I think that's probably the only way to get upstream to take up
our case.
next prev parent reply other threads:[~2024-09-03 5:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 17:53 CIFS lockup regression on SMB1 in 6.10 matoro
2024-08-15 19:37 ` Steve French
2024-08-15 21:22 ` matoro
2024-08-16 3:31 ` Steve French
2024-08-16 3:47 ` matoro
2024-08-20 19:33 ` Kris Karas (Bug Reporting)
[not found] ` <CAH2r5mugVqy=jd_9x1xKYym6id1F2O-QuSX8C0HKbZPHybgCDQ@mail.gmail.com>
2024-08-23 20:51 ` Kris Karas (Bug Reporting)
2024-09-03 4:55 ` matoro [this message]
[not found] ` <CAH2r5mtDbD2uNdodE5WsOmzSoswn67eHAqGVjZJPHbX1ipkhSw@mail.gmail.com>
2024-09-05 14:40 ` Kris Karas (Bug Reporting)
[not found] ` <2322699.1725442054@warthog.procyon.org.uk>
[not found] ` <c8027078-bd61-449e-8199-908af20b1f10@moonlit-rail.com>
2024-09-05 15:40 ` Kris Karas (Bug Reporting)
2024-09-14 22:15 ` matoro
2024-09-15 0:51 ` Kris Karas (Bug Reporting)
[not found] ` <CAH2r5mtEdn5tWBn3cs6chxxRdWNT1VFjYwYcsWU7sZkAqsW8rw@mail.gmail.com>
2024-09-15 0:57 ` Fwd: " 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=2925a37f946d1b96a7251f7be72ba341@matoro.tk \
--to=matoro_mailinglist_kernel@matoro.tk \
--cc=bruno@clisp.org \
--cc=bugs-a21@moonlit-rail.com \
--cc=linux-cifs@vger.kernel.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