From: Wei Liu <wei.liu@kernel.org>
To: "Andrea Parri (Microsoft)" <parri.andrea@gmail.com>
Cc: KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Michael Kelley <mikelley@microsoft.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Wilczynski <kw@linux.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] PCI: hv: Hardening changes
Date: Fri, 13 May 2022 16:58:46 +0000 [thread overview]
Message-ID: <20220513165846.ss26oqo3prhk3h3s@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20220511223207.3386-1-parri.andrea@gmail.com>
On Thu, May 12, 2022 at 12:32:05AM +0200, Andrea Parri (Microsoft) wrote:
> Changes since v1[1]:
> - Add validation in q_resource_requirements()
>
> Patch #2 depends on changes in hyperv-next. (Acknowledging that hyperv
> is entering EOM, for review.)
>
> Thanks,
> Andrea
>
> [1] https://lkml.kernel.org/r/20220504125039.2598-1-parri.andrea@gmail.com
>
> Andrea Parri (Microsoft) (2):
> PCI: hv: Add validation for untrusted Hyper-V values
> PCI: hv: Fix synchronization between channel callback and
> hv_pci_bus_exit()
Applied to hyperv-next. Thanks.
prev parent reply other threads:[~2022-05-13 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 22:32 [PATCH v2 0/2] PCI: hv: Hardening changes Andrea Parri (Microsoft)
2022-05-11 22:32 ` [PATCH v2 1/2] PCI: hv: Add validation for untrusted Hyper-V values Andrea Parri (Microsoft)
2022-05-12 15:08 ` Michael Kelley (LINUX)
2022-05-11 22:32 ` [PATCH v2 2/2] PCI: hv: Fix synchronization between channel callback and hv_pci_bus_exit() Andrea Parri (Microsoft)
2022-05-13 10:11 ` [PATCH v2 0/2] PCI: hv: Hardening changes Lorenzo Pieralisi
2022-05-13 16:51 ` Wei Liu
2022-05-13 16:58 ` Wei Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220513165846.ss26oqo3prhk3h3s@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bhelgaas@google.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mikelley@microsoft.com \
--cc=parri.andrea@gmail.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).