From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Davyd McColl <davydm@gmail.com>,
Steve French <smfrench@gmail.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c
Date: Wed, 2 Mar 2022 16:50:47 -0800 [thread overview]
Message-ID: <CAHk-=wjSBvRk-ksUBOiQzJd=e19UZKvOSZs1UHahK5U0QVh6RQ@mail.gmail.com> (raw)
In-Reply-To: <fe156bb6-c6d2-57da-7f62-57d2972bf1ae@leemhuis.info>
On Tue, Mar 1, 2022 at 10:58 PM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> Thx for the update. I pointed Linus towards this thread two times now,
> but he didn't comment on it afaics. CCing him now, maybe that will to
> the trick.
So I have to admit that I think it's a 20+ year old legacy and
insecure protocol that nobody should be using.
When the maintainer can't really even test it, and it really has been
deprecated that long, I get the feeling that somebody who wants it to
be maintained will need to do that job himself.
This seems to be a _very_ niche thing, possibly legacy museum style
equipment, and maybe using an older kernel ends up being the answer if
nobody steps up and maintains it as an external patch.
Linus
next prev parent reply other threads:[~2022-03-03 0:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 6:06 Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c Davyd McColl
2022-01-10 14:11 ` Thorsten Leemhuis
2022-01-10 17:31 ` Steve French
2022-01-10 20:30 ` Davyd McColl
2022-01-10 22:13 ` Steve French
2022-01-11 6:45 ` Davyd McColl
2022-01-11 21:51 ` Steve French
2022-01-11 23:26 ` Steve French
2022-01-12 2:32 ` ronnie sahlberg
2022-01-12 5:49 ` Davyd McColl
2022-01-28 13:30 ` Thorsten Leemhuis
2022-01-28 13:39 ` Davyd McColl
2022-01-28 13:50 ` ronnie sahlberg
2022-01-28 14:02 ` Thorsten Leemhuis
2022-01-28 14:23 ` ronnie sahlberg
2022-02-18 13:30 ` Davyd McColl
2022-03-02 6:58 ` Thorsten Leemhuis
2022-03-02 17:28 ` Davyd McColl
2022-03-03 0:50 ` Linus Torvalds [this message]
2022-03-03 1:27 ` Steve French
2022-03-04 6:43 ` Thorsten Leemhuis
2022-07-27 20:04 ` Clemens Leu
2022-07-28 2:27 ` Steve French
[not found] <D58238A4-F04E-458E-AB05-4A74235B2C65@getmailspring.com>
2022-01-10 12:15 ` Thorsten Leemhuis
2022-01-11 3:16 ` Steve French
2022-10-14 19:58 ` Carsten Langer
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='CAHk-=wjSBvRk-ksUBOiQzJd=e19UZKvOSZs1UHahK5U0QVh6RQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=davydm@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
/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).