Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: David Howells <dhowells@redhat.com>, Steve French <smfrench@gmail.com>
Cc: matoro <matoro_mailinglist_kernel@matoro.tk>,
	Bruno Haible <bruno@clisp.org>,
	Linux Cifs <linux-cifs@vger.kernel.org>
Subject: Re: CIFS lockup regression on SMB1 in 6.10
Date: Thu, 5 Sep 2024 11:40:42 -0400	[thread overview]
Message-ID: <97a71be9-d274-4e9e-9928-dce062ba2a22@moonlit-rail.com> (raw)
In-Reply-To: <c8027078-bd61-449e-8199-908af20b1f10@moonlit-rail.com>

Kris Karas wrote:
> David Howells wrote:
>> The attached may help.
> 
> Thanks.  Gave it a whirl.  Alas, FTBFS against 6.10.8:

OK, I tried this against git master, compiles fine there.
Success!  The lockup with vers=1.0/unix is gone for me.

Just need a backport for 6.10.x to fix the missing NETFS_SREQ_HIT_EOF 
and rdata->actual_len.

Thanks!
Kris


  parent reply	other threads:[~2024-09-05 16:01 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
     [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) [this message]
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=97a71be9-d274-4e9e-9928-dce062ba2a22@moonlit-rail.com \
    --to=bugs-a21@moonlit-rail.com \
    --cc=bruno@clisp.org \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=matoro_mailinglist_kernel@matoro.tk \
    --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