All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Elliott Mitchell <ehem+xen@m5p.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Henry Wang <Henry.Wang@arm.com>,
	xen-devel@lists.xenproject.org,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Neowutran <xen@neowutran.ovh>
Subject: Re: [PATCH] x86/x2apic: introduce a mixed physical/cluster mode
Date: Mon, 27 Nov 2023 09:27:18 +0100	[thread overview]
Message-ID: <ZWRS5qUTjkoD22MF@macbook> (raw)
In-Reply-To: <ZWFKtrBl2kpdvjBC@mattapan.m5p.com>

On Fri, Nov 24, 2023 at 05:15:34PM -0800, Elliott Mitchell wrote:
> On Thu, Nov 23, 2023 at 10:39:37AM +0100, Roger Pau Monné wrote:
> > On Tue, Nov 21, 2023 at 04:56:47PM -0800, Elliott Mitchell wrote:
> > > It was insisted that full logs be sent to xen-devel.  Perhaps I am
> > > paranoid, but I doubt I would have been successful at scrubbing all
> > > hardware serial numbers.  As such, I was willing to post substantial
> > > sections, but not everything.
> > 
> > Can you please point out which hardware serial numbers are you
> > referring to, and where are they printed in Xen dmesg?
> 
> I didn't confirm the presence of hardware serial numbers getting into
> Xen's dmesg, but there was a lot of data and many hexadecimal numbers.
> With 4000 lines of output, checking for concerning data is troublesome.

4000 lines of output from Xen dmesg seems quite suspicious.  Xen dmesg
on a fully booted box is ~400 lines on my local box.  That might get
quite longer if you have a box with a lot of memory region, or a lot
of CPUs.

> There was enough for alarms to trigger.

That's fine, but without pointing out which information is sensitive,
it's very unlikely such concerns will ever get fixed.

Could you at least go over the log and point out the first instance of
such line that you consider contains sensitive information?

The primary way we have to diagnose and solve issues reported by users
is based on Xen dmesg, so if it's impossible to provide it for privacy
reasons that's an issue that we need to address.

Regards, Roger.


  reply	other threads:[~2023-11-27  8:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 13:51 [PATCH] x86/x2apic: introduce a mixed physical/cluster mode Roger Pau Monne
2023-10-30 14:32 ` Jan Beulich
2023-10-30 16:10   ` Roger Pau Monné
2023-10-30 16:34     ` Jan Beulich
2023-10-30 16:38       ` Roger Pau Monné
2023-10-30 14:50 ` Elliott Mitchell
2023-10-30 15:27   ` Roger Pau Monné
2023-11-01  1:05     ` Elliott Mitchell
2023-11-07 19:35     ` Elliott Mitchell
2023-11-17 10:12       ` Neowutran
2023-11-18  3:04         ` Elliott Mitchell
2023-11-18 11:33           ` Andrew Cooper
2023-11-22  0:56             ` Elliott Mitchell
2023-11-23  9:39               ` Roger Pau Monné
2023-11-25  1:15                 ` Elliott Mitchell
2023-11-27  8:27                   ` Roger Pau Monné [this message]
2023-12-04  1:02                     ` Elliott Mitchell
2023-12-04  8:03                       ` Jan Beulich
2023-12-04 11:07                       ` Roger Pau Monné
2023-11-24 19:54             ` Neowutran
2023-11-27 11:49               ` Andrew Cooper
2023-11-27 14:53                 ` Roger Pau Monné
2023-11-27 15:56                   ` Andrew Cooper
2023-11-27 15:18           ` Neowutran
2023-11-27 16:17             ` Andrew Cooper

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=ZWRS5qUTjkoD22MF@macbook \
    --to=roger.pau@citrix.com \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ehem+xen@m5p.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xen@neowutran.ovh \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.