From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Paulo Alcantara <pc@cjr.nz>, Moritz Duge <duge@pre-sense.de>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Aurelien Aptel <aaptel@suse.com>,
Ronnie Sahlberg <lsahlber@redhat.com>,
Steve French <stfrench@microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32)
Date: Wed, 4 May 2022 18:43:47 +0200 [thread overview]
Message-ID: <29f90334-53dc-4926-fc38-420b4d024f1b@leemhuis.info> (raw)
In-Reply-To: <87zgjx1d09.fsf@cjr.nz>
On 04.05.22 18:25, Paulo Alcantara wrote:
> Moritz Duge <duge@pre-sense.de> writes:
>
>> I'm still waiting for a reply from Paul.
>
> The bug is currently being handled at [1]. Enzo has also asked you to
> send us network traces in [2] and you haven't sent any, yet.
Many thx for the update.
> I'm not "Paul", BTW.
Paulo, please accept my apologies, that was my fault.
> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1194945
> [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1194945#c13
#regzbot link: https://bugzilla.opensuse.org/show_bug.cgi?id=1194945
Ciao, Thorsten
next prev parent reply other threads:[~2022-05-04 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:08 Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32) Thorsten Leemhuis
2022-05-04 13:19 ` Thorsten Leemhuis
2022-05-04 16:12 ` Moritz Duge
2022-05-04 16:25 ` Paulo Alcantara
2022-05-04 16:43 ` Thorsten Leemhuis [this message]
2022-05-20 7:38 ` Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32) #forregzbot Thorsten Leemhuis
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=29f90334-53dc-4926-fc38-420b4d024f1b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aaptel@suse.com \
--cc=duge@pre-sense.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=pc@cjr.nz \
--cc=regressions@lists.linux.dev \
--cc=stfrench@microsoft.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.