archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: "" <>
Subject: Re: Regression: CIFS umount fails since 14302ee33 with some servers (exit code 32) #forregzbot
Date: Fri, 20 May 2022 09:38:05 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 04.05.22 18:43, Thorsten Leemhuis wrote:
> On 04.05.22 18:25, Paulo Alcantara wrote:
>> Moritz Duge <> 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]
>> [2]
> #regzbot link:

#regzbot invalid: likely solved, likely by 5d7e282541fc ("cifs: do not
skip link targets when an I/O fails")

To quote

> The problem disappeared with one of the latest openSUSE kernel updates.
> It must have been one of these:
> 2022-04-06: ​5.3.18-150300.59.63
> ​2022-05-05: 5.3.18-150300.59.68
> I didn't do a bisect. But the following commit, contained in SUSE kernel 5.3.18-150300.59.68, seems most likely to me.
> SUSE kernel:
> SUSE kernel source:
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.


      reply	other threads:[~2022-05-20  7:38 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
2022-05-20  7:38         ` Thorsten Leemhuis [this message]

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).