From: Elliott Mitchell <ehem+xen@m5p.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Kelly Choi" <kelly.choi@cloud.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Serious AMD-Vi(?) issue
Date: Tue, 14 May 2024 13:51:28 -0700 [thread overview]
Message-ID: <ZkPO0D0/Jx4ZnRBO@mattapan.m5p.com> (raw)
In-Reply-To: <08503965-4ba9-4fe3-a176-895623f4ad92@suse.com>
On Tue, May 14, 2024 at 10:22:51AM +0200, Jan Beulich wrote:
> On 13.05.2024 22:11, Elliott Mitchell wrote:
> > On Mon, May 13, 2024 at 10:44:59AM +0200, Roger Pau Monné wrote:
> >> Why do you mask the device SBDF in the above snippet? I would really
> >> like to understand what's so privacy relevant in a PCI SBDF number.
> >
> > I doubt it reveals much. Simply seems unlikely to help debugging and
> > therefore I prefer to mask it.
>
> SBDF in one place may be matchable against a memory address in another
> place. _Any_ hiding of information is hindering analysis. Please can
> you finally accept that it needs to be the person doing the analysis
> to judge what is or is not relevant to them?
Not going to happen as I'd accepted this long ago. The usual approach
is all developers have PGP keys (needed for security issues anyway) and
you don't require all logs to be public.
I've noticed the core of the Xen project appears centered in the EU. Yet
you're not catering to data privacy at all? Or is this a service
exclusively provided to people who prove they're EU citizens?
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
next prev parent reply other threads:[~2024-05-14 20:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 20:24 Serious AMD-Vi issue Elliott Mitchell
2024-02-12 23:23 ` Elliott Mitchell
2024-03-04 19:56 ` Elliott Mitchell
2024-03-18 19:41 ` Serious AMD-Vi(?) issue Elliott Mitchell
2024-03-22 16:41 ` Kelly Choi
2024-03-22 19:22 ` Elliott Mitchell
2024-03-25 7:55 ` Jan Beulich
2024-03-25 21:43 ` Elliott Mitchell
2024-03-27 17:27 ` Elliott Mitchell
2024-03-28 6:25 ` Jan Beulich
2024-03-28 15:22 ` Elliott Mitchell
2024-03-28 16:17 ` Elliott Mitchell
2024-04-11 2:41 ` Elliott Mitchell
2024-04-17 12:40 ` Jan Beulich
2024-04-18 6:45 ` Elliott Mitchell
2024-04-18 7:09 ` Jan Beulich
2024-04-19 4:33 ` Elliott Mitchell
2024-05-11 4:09 ` Elliott Mitchell
2024-05-13 8:44 ` Roger Pau Monné
2024-05-13 20:11 ` Elliott Mitchell
2024-05-14 8:22 ` Jan Beulich
2024-05-14 20:51 ` Elliott Mitchell [this message]
2024-05-15 13:40 ` Kelly Choi
2024-05-16 5:21 ` Elliott Mitchell
2024-05-14 8:20 ` Jan Beulich
2024-03-04 23:55 ` AMD-Vi issue Andrew Cooper
2024-03-05 0:34 ` Elliott Mitchell
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=ZkPO0D0/Jx4ZnRBO@mattapan.m5p.com \
--to=ehem+xen@m5p.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=kelly.choi@cloud.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).