netdev - Re: [PATCH net-next] liquidio: fix hang when re-binding VF host drv after running DPDK VF driver

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-prev] [day] [month] [year] [list]

Message-Id: <20180716.140210.2066723355300245370.davem@davemloft.net>
Date:   Mon, 16 Jul 2018 14:02:10 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     felix.manlunas@...ium.com
Cc:     netdev@...r.kernel.org, raghu.vatsavayi@...ium.com,
        derek.chickles@...ium.com, satananda.burla@...ium.com,
        ricardo.farrington@...ium.com
Subject: Re: [PATCH net-next] liquidio: fix hang when re-binding VF host
 drv after running DPDK VF driver

From: Felix Manlunas <felix.manlunas@...ium.com>
Date: Fri, 13 Jul 2018 12:50:21 -0700

> From: Rick Farrington <ricardo.farrington@...ium.com>
> 
> When configuring SLI_PKTn_OUTPUT_CONTROL, VF driver was assuming that IPTR
> mode was disabled by reset, which was not true.  Since DPDK driver had
> set IPTR mode previously, the VF driver (which uses buf-ptr-only mode) was
> not properly handling DROQ packets (i.e. it saw zero-length packets).
> 
> This represented an invalid hardware configuration which the driver could
> not handle.
> 
> Signed-off-by: Rick Farrington <ricardo.farrington@...ium.com>
> Signed-off-by: Felix Manlunas <felix.manlunas@...ium.com>

Applied.