Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp4698992pxb; Tue, 31 Aug 2021 11:05:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzGh4PoIxpn0VoTq4ti7Xq79QPIhknqxeYUP21+tAcgE+ADnKG+SQXp0kKDiu7hvpbGvrWK X-Received: by 2002:a05:6402:139a:: with SMTP id b26mr24702815edv.301.1630433144780; Tue, 31 Aug 2021 11:05:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630433144; cv=none; d=google.com; s=arc-20160816; b=iplqYYL3DJtp2dIj88Lu3wOaHxk5MP2YjCga+4Z601qGcS/MgHNQagDMrW8tU/Ntvz tfGFWP3+KyWnhJ9lpozspdoNQZuWaI0NTLsysXHkQMqaVqgM7Wukkczx8Qr+QufOU0lR gOu9UvR+R1EnNJ6JU6GM/2DZWCcxAmHqIAMfb/GQwTMNgOcmD7UAuISUfDMxOqHVeaEU 1KzjOK4U/80XxUmvG1DSy4sUAT7Tw2BsZhtW8M3SCAd2gI3x0End3mUrUY+UB2ZQDZN7 mWRGO/vZtRfLVpMvnw6Lt48JwID3h92nIqvOUeDt8ndyorEwHeoVHKZ8vs6JEg7tw6SO NnUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=PlDvXWCwq9oQrcS+ObUACbXbifYYVn7FARrjhr/5Hw8=; b=DtIHTrFg4engHR7hiHCyMB6cdvGDg7lc+A8/pc8CydUTG8Ur6GZY29RlCoRFd3NgCx C5SXaHsV/uOhLYna02j4Vgc5QJ7slV/toph5eY3A0I53E3WjQtddwbrp/4pI9qPq2rza E/6cc44XxJHk+BYsnT65TWEaNf06GMZ8+zA4l2+dAcXfetL3UVTZTWq/0q25L5EWpTHy SyiO5T8kjv5/dcaJy3IlqG6OdGK8aQrmsO9yK5lsIv8Y1Q6nDTfw7y3/ZU6uMhbs3f70 53dRtg1vHdzqHePhBgzNITIQumu3crFfC5Xv5nndQ8NpbCIYIDyCLvlwwRx7pIhV6Q1m zUfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=google header.b=LaDPyL+b; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m1si11881895ejj.616.2021.08.31.11.05.21; Tue, 31 Aug 2021 11:05:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=google header.b=LaDPyL+b; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240075AbhHaQk7 (ORCPT + 99 others); Tue, 31 Aug 2021 12:40:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39816 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232509AbhHaQk6 (ORCPT ); Tue, 31 Aug 2021 12:40:58 -0400 Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BDAA2C061575 for ; Tue, 31 Aug 2021 09:40:02 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id g14so4791803ljk.5 for ; Tue, 31 Aug 2021 09:40:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PlDvXWCwq9oQrcS+ObUACbXbifYYVn7FARrjhr/5Hw8=; b=LaDPyL+bvAPyD4iPhWTnGEliAF5N5bk9qNdn6gNkd/k4E9TXbp/ff4JtgKOD8IS41y 9mfNzGlYM+qCWBkM3Xu6bQ0IZ4fcrj9gBV7prm6Ry88aItm9Up1BB36d6W2KxRIOCtWI LxLJxns5SrPZu9HOj88MgI//jXoAE0XHqJ6BQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PlDvXWCwq9oQrcS+ObUACbXbifYYVn7FARrjhr/5Hw8=; b=Gbvjnc3u5yrCvn1fWvf7HaCQDfydHmoaNrr6kW+0iPFZTQtGDxURTo0KQDQ29gmSH5 I4JqaD9GTnYqiHvKnyh7I75R6udcEUD0Sj/CtPnNq4oLpKsVSUqdj/6IyCdtJglzQnK6 Xfa5Gr77blyltXLkvj6v+65+lnLrvqR8HgwXqZyBpJB3iw4Leh3C0lFLhqM51botOiUR AqmrR/W8/eUNnlMetBSPCswnBbJwpvP5ufu2SQNvCV0s0z9ZmZGMSQTnpEyS+y0lF7gn vOUfh7ZQPtb8Vtcda7HOjdsckc6ZOfftbDDw1mKYKErV2szr7sjTco1DCeMgZHU20Erx YftA== X-Gm-Message-State: AOAM533KqkmrC4x2hoRgC0zARcm4SVl5avpZISUm9oYBNZQSCwYLYEkl kcbr8Sw5YAeBq0r2efJR62x5dpFjyhYuFqbqTqU= X-Received: by 2002:a2e:a28d:: with SMTP id k13mr24398607lja.446.1630428000748; Tue, 31 Aug 2021 09:40:00 -0700 (PDT) Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com. [209.85.167.47]) by smtp.gmail.com with ESMTPSA id j1sm1455553lja.108.2021.08.31.09.39.59 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 31 Aug 2021 09:39:59 -0700 (PDT) Received: by mail-lf1-f47.google.com with SMTP id x27so62805lfu.5 for ; Tue, 31 Aug 2021 09:39:59 -0700 (PDT) X-Received: by 2002:a05:6512:1053:: with SMTP id c19mr9701063lfb.201.1630427999490; Tue, 31 Aug 2021 09:39:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Linus Torvalds Date: Tue, 31 Aug 2021 09:39:42 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [GIT PULL] cifs/smb3 client fixes To: Steve French Cc: LKML , CIFS Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 29, 2021 at 10:48 PM Steve French wrote: > > - mostly restructuring to allow disabling less secure algorithms (this > will allow eventual removing rc4 and md4 from general use in the > kernel) Well, you should probably have mentioned that you already started on this by removing LANMAN support. I'm sincerely hoping nobody used or depended on that old garbage in this day and age any more. Anyway, entirely unrelated question: you pretty much interchangeably use "cifs" or "smb3" for the filesystem, as shown once more by the commit messages here (but also the subject line). The filesystem directory is called "cifs", and I've taken to use that in my "Pull cifs updates" thing from you to just avoiding the confusion. And now we have ksmbd (yup, I just merged that pull request too), so we have a "cifs client" and a "smb server". Aaarrgh. I understand that some people may care about the name, may care about "smb2 vs smb3", or whatever. But I have to admit finding it a bit annoying how the code and the directory layout uses these different terms pretty much randomly with no real apparent logic. Somehow the NFS people had no problem completely changing everything about their protocols and then still calling the end result "nfs client" vs "nfs server". Oh well. I'm assuming it's not going to change, and it's not really a problem, I just wanted to mention my frustration about how clear as mud the naming is. Linus