archive mirror
 help / color / mirror / Atom feed
From: Moritz Duge <>
To: Thorsten Leemhuis <>,
	"Paulo Alcantara (SUSE)" <>
Cc: "" <>,
	Aurelien Aptel <>,
	Ronnie Sahlberg <>,
	Steve French <>,
	Linux Kernel Mailing List <>,
	"" <>
Subject: Re: Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32)
Date: Wed, 4 May 2022 18:12:22 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1.1: Type: text/plain, Size: 1008 bytes --]

Hi Thorsten,

I'm still waiting for a reply from Paul.

I'm not a kernel developer and I reported everything I know about
the bug. Including the result of a Git bisect, showing the
problematic commit.

So currently I don't see much else I can do.

Kind regards,

Am 04.05.22 um 15:19 schrieb Thorsten Leemhuis:
> Hi, this is your Linux kernel regression tracker. Top-posting for once,
> to make this easily accessible to everyone.
> Paul, Moritz, what's the status here? It seems nothing happened at all
> since below mail. Was the issue fixed? Or did it fall through the cracks?
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> #regzbot poke

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3995 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-05-04 16:22 UTC|newest]

Thread overview: 5+ 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 [this message]
2022-05-04 16:25     ` Paulo Alcantara
2022-05-04 16:43       ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).