linux-kernel - Re: [PATCH 1/2] cdc_ncm: Implement the 32-bit version of NCM Transfer Block

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20200313.204354.1099710416713347967.davem@davemloft.net>
Date:   Fri, 13 Mar 2020 20:43:54 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     bay@...kerdom.ru
Cc:     oliver@...kum.org, gregkh@...uxfoundation.org, info@...ux.net,
        tglx@...utronix.de, kstewart@...uxfoundation.org,
        linux-usb@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] cdc_ncm: Implement the 32-bit version of NCM
 Transfer Block

From: Alexander Bersenev <bay@...kerdom.ru>
Date: Sat, 14 Mar 2020 02:38:20 +0500

> The NCM specification defines two formats of transfer blocks: with 16-bit
> fields (NTB-16) and with 32-bit fields (NTB-32). Currently only NTB-16 is
> implemented.
> 
> This patch adds the support of NTB-32. The motivation behind this is that
> some devices such as E5785 or E5885 from the current generation of Huawei
> LTE routers do not support NTB-16. The previous generations of Huawei
> devices are also use NTB-32 by default.
> 
> Also this patch enables NTB-32 by default for Huawei devices.
> 
> During the 2019 ValdikSS made five attempts to contact Huawei to add the
> NTB-16 support to their router firmware, but they were unsuccessful.
> 
> Signed-off-by: Alexander Bersenev <bay@...kerdom.ru>

This patch is already in my net-next tree.

You need to submit the follow-up fix all by itself, relative to my
net-next GIT tree.

You must always post patches against the GIT tree that your change
is targetting, that way you will avoid situations like this.

Thank you.