linux-kernel - Re: [PATCH] xen: introduce xen_vring_use

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: <alpine.DEB.2.22.394.2407301519330.4857@ubuntu-linux-20-04-desktop>
Date: Tue, 30 Jul 2024 15:29:54 -0700 (PDT)
From: Stefano Stabellini <sstabellini@...nel.org>
To: Amneesh Singh <a-singh21@...com>, mst@...hat.com
cc: sstabellini@...nel.org, boris.ostrovsky@...cle.com, hch@...radead.org, 
    iommu@...ts.linux-foundation.org, jasowang@...hat.com, jgross@...e.com, 
    konrad.wilk@...cle.com, linux-arm-kernel@...ts.infradead.org, 
    linux-imx@....com, linux-kernel@...r.kernel.org, peng.fan@....com, 
    virtualization@...ts.linux-foundation.org, x86@...nel.org, 
    xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma

On Tue, 30 Jul 2024, Amneesh Singh wrote:
> Hi Stefano,
> 
> First off, apologies for bumping this dead thread.
> 
> I came across this patch signed off by you recently
> https://github.com/Xilinx/linux-xlnx/commit/72cb5514953be3aa2ac00c57c9eaa100ecc67176
> 
> and was wondering if a patch replacing xen_domain() with xen_pv_domain() in
> vring_use_dma_api() can be sent upstream? If not, is there a reason why?

Hi Amneesh,

Yes this patch is still required for Xen on ARM and it fixes a real bug.
Unfortunately the upstreaming process stalled so we had to keep the fix
in our Xilinx Linux branch. Here is the link to the start of this
conversation and to the last message:

https://marc.info/?i=20200624091732.23944-1-peng.fan%40nxp.com
https://marc.info/?i=alpine.DEB.2.21.2007151001140.4124%40sstabellini-ThinkPad-T480s


Hi Michael, I see you are CCed to this email. Would you be open to
acking this patch now that a 3rd independent engineer from a different
company (NXP first, then AMD/Xilinx, now TI) has reported this as a bug
fix?