From: "Kleen, Andi" <andi.kleen@intel.com>
To: Robert Buhren <robert.buhren@sect.tu-berlin.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Radev, Martin" <martin.radev@aisec.fraunhofer.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"doshir@vmware.com" <doshir@vmware.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Morbitzer, Mathias" <mathias.morbitzer@aisec.fraunhofer.de>,
"file@sect.tu-berlin.de" <file@sect.tu-berlin.de>,
"Banse, Christian" <christian.banse@aisec.fraunhofer.de>,
"brijesh.singh@amd.com" <brijesh.singh@amd.com>,
"Thomas.Lendacky@amd.com" <Thomas.Lendacky@amd.com>,
"pv-drivers@vmware.com" <pv-drivers@vmware.com>,
"martin.b.radev@gmail.com" <martin.b.radev@gmail.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: RE: Security issue with vmxnet3 and e100 for AMD SEV(-SNP) / Intel TDX
Date: Mon, 11 Jan 2021 17:24:02 +0000 [thread overview]
Message-ID: <719473c603774460970f93d926530b87@intel.com> (raw)
In-Reply-To: <749d3ace-877f-1c5c-bb00-ffcb8394f36a@sect.tu-berlin.de>
>Let us know if you are interested in our fuzzing/static analysis setup.
>We're planning to submit a paper soon and we will publish the source >code along with the paper.
We already have an own static analysis/fuzzing frame work, but it's not released yet.
-Andi
prev parent reply other threads:[~2021-01-11 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM7P194MB0900E443CEBD6EF2EE37325ED9AE0@AM7P194MB0900.EURP194.PROD.OUTLOOK.COM>
[not found] ` <AM7P194MB09004AD790C5C85EDCB42323D9AE0@AM7P194MB0900.EURP194.PROD.OUTLOOK.COM>
2021-01-11 13:26 ` Security issue with vmxnet3 and e100 for AMD SEV(-SNP) / Intel TDX Kirill A. Shutemov
2021-01-11 13:56 ` Robert Buhren
2021-01-11 17:24 ` Kleen, Andi [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=719473c603774460970f93d926530b87@intel.com \
--to=andi.kleen@intel.com \
--cc=Thomas.Lendacky@amd.com \
--cc=anthony.l.nguyen@intel.com \
--cc=brijesh.singh@amd.com \
--cc=christian.banse@aisec.fraunhofer.de \
--cc=doshir@vmware.com \
--cc=file@sect.tu-berlin.de \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=martin.b.radev@gmail.com \
--cc=martin.radev@aisec.fraunhofer.de \
--cc=mathias.morbitzer@aisec.fraunhofer.de \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=robert.buhren@sect.tu-berlin.de \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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).