From: "Linux kernel regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Ronnie Sahlberg <lsahlber@redhat.com>,
Steve French <stfrench@microsoft.com>
Subject: CIFS NTLM regression still annoying people (was: Re: Linux regressions report for mainline [2023-01-29])
Date: Mon, 30 Jan 2023 12:04:23 +0100 [thread overview]
Message-ID: <62fb7c9a-179a-f3f0-93b6-5e74f88dad63@leemhuis.info> (raw)
In-Reply-To: <CAHk-=wgnBBJ7hDSz5T+2FMF0JhE1Jmf6=tZEytQ6n1jZ4m2s=w@mail.gmail.com>
On 29.01.23 20:32, Linus Torvalds wrote:
> On Sun, Jan 29, 2023 at 9:42 AM Regzbot (on behalf of Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>>
>> * Andrew afaics didn’t sent a revert[1] from Vlastimir your way
> Ok, I applied this one as tiny and clear and hitting actual user loads.
Great, many thx!
>> * A fix[1] for a stack_depot/kmemleak issue is in next for a while already too[2]
> This one I left alone, since it's a bit more involved and the use-case
> is more esoteric too.
Totally fine with me and yeah, a bit esoteric. But when somebody bisects
and report a problem (in this case: Boris) that already fixed in next
for a few days, my mind yells "what a waste or energy, this could have
been prevented by mainlining the fix a bit more quickly" -- that's why I
brought it up.
> And in other news, the input regression revert you mentioned earlier
> got pulled this morning.
Ahh, great.
BTW, there is one thing that still bugs me: every few weeks there is yet
somebody new[1] complaining about the removal of support for NTLM and
weaker authentication algorithms from cifs some time ago in
76a3c92ec9e0. The situation[2] was improved slightly in 2f6f19c7aaad
("cifs: fix regression in very old smb1 mounts"), but it seems some
users of Apple Time Capsules or some Epson printer/scanner still can't
access their devices which apparently still work fine in Windows and
macOS[1].
Yes, the issue is tricky, as there are security implications here and we
have nobody that tests this, as you pointed out [3]. Is there
nevertheless something somebody committed could do? Would we even be
willing to add that support back in, in case someone commits to maintain
and regularly test that codepath?
Ciao, Thorsten
[1] https://bugzilla.kernel.org/show_bug.cgi?id=216682
[2] https://bugzilla.kernel.org/show_bug.cgi?id=215375
[3]
https://lore.kernel.org/all/CAHk-=wjSBvRk-ksUBOiQzJd=e19UZKvOSZs1UHahK5U0QVh6RQ@mail.gmail.com/
prev parent reply other threads:[~2023-01-30 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:42 Linux regressions report for mainline [2023-01-29] Regzbot (on behalf of Thorsten Leemhuis)
2023-01-29 19:32 ` Linus Torvalds
2023-01-30 11:04 ` Linux kernel regression tracking (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=62fb7c9a-179a-f3f0-93b6-5e74f88dad63@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=stfrench@microsoft.com \
--cc=torvalds@linux-foundation.org \
/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).