From: Thorsten Leemhuis <writing@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
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: <b6dcde8e-b944-b222-7cff-5caef418638e@leemhuis.info> (raw)
In-Reply-To: <29f90334-53dc-4926-fc38-420b4d024f1b@leemhuis.info>
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 <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
#regzbot invalid: likely solved, likely by 5d7e282541fc ("cifs: do not
skip link targets when an I/O fails")
To quote
https://bugzilla.kernel.org/show_bug.cgi?id=215782#c2
> 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.
>
> kernel.org
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=5d7e282541fc91b831a5c4477c5d72881c623df9
>
> SUSE kernel:
> https://github.com/SUSE/kernel/commit/f6c7673fbee1985e8fcfe4936ca6d91852f86b13
>
> SUSE kernel source:
> https://github.com/SUSE/kernel-source/commit/e7007189db138241fce6440c3bcfa084a0cf7c72
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.
Ciao,
prev parent 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:
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=b6dcde8e-b944-b222-7cff-5caef418638e@leemhuis.info \
--to=writing@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).