linux-kernel - Re: [EXTERNAL] Re: linux-next: build failure after merge of the net-next tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 16 Dec 2020 21:07:35 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Steven French <Steven.French@...rosoft.com>
Cc:     David Miller <davem@...emloft.net>,
        Networking <netdev@...r.kernel.org>,
        Jakub Kicinski <kuba@...nel.org>,
        Samuel Cabrero <scabrero@...e.de>,
        Francis Laniel <laniel_francis@...vacyrequired.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        "linux-cifs@...r.kernel.org" <linux-cifs@...r.kernel.org>
Subject: Re: [EXTERNAL] Re: linux-next: build failure after merge of the
 net-next tree

Hi Steven,

On Wed, 16 Dec 2020 02:21:26 +0000 Steven French <Steven.French@...rosoft.com> wrote:
>
> I applied your patch to the tip of my tree (cifs-2.6.git for-next) -
> hopefully that makes it easier when I sent the PR in a day or two for
> cifs/smb3 changes.

I think you have just made your tree fail to build as nla_strscpy does
not exist in your tree ... Just remove that commit and tell Linus about
the necessary change and he can add it to the merge.

And, no, rebasing your tree in Linus', or even doing a merge with
Linus' tree is not really a reasonable option at this point.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped