From: "Linux kernel regression tracking (#adding)" <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Bug 216889 - CIFS 1.0 mount succeeds but any attempt to read from / write to the share fails
Date: Fri, 6 Jan 2023 10:56:03 +0100 [thread overview]
Message-ID: <366a47b4-b530-68c2-992d-c2861a8add5c@leemhuis.info> (raw)
[TLDR: Just adding a regression reported to bko to the tracking]
I noticed a regression reported in bugzilla.kernel.org that seems to be
handled there already, nevertheless I'd like to add to the tracking to
ensure it's doesn't fall through the cracks in the end:
#regzbot introduced: v6.0..v6.1
https://bugzilla.kernel.org/show_bug.cgi?id=216889
#regzbot title: cifs: CIFS 1.0 mount succeeds but any attempt to read
from / write to the share fails
#regzbot ignore-activity
Regression is also in stable, to quote:
> 6.0.15 works fine - 6.0.16 doesn't.
/me sooner or later needs to modify regzbot to handle such situations better
See the ticket for details, there were a few replies already.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
reply other threads:[~2023-01-06 9:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=366a47b4-b530-68c2-992d-c2861a8add5c@leemhuis.info \
--to=regressions@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).