From: "Tobin C. Harding" <me@tobin.cc>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: rkrcmar@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: remove printing of token address
Date: Mon, 9 Oct 2017 21:04:15 +1100 [thread overview]
Message-ID: <20171009100415.GA12785@eros> (raw)
In-Reply-To: <1845029054.11118038.1507535378802.JavaMail.zimbra@redhat.com>
On Mon, Oct 09, 2017 at 03:49:38AM -0400, Paolo Bonzini wrote:
>
>
> ----- Original Message -----
> > From: "Tobin C. Harding" <me@tobin.cc>
> > To: "Paolo Bonzini" <pbonzini@redhat.com>, rkrcmar@redhat.com
> > Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, "Tobin C. Harding" <me@tobin.cc>
> > Sent: Monday, October 9, 2017 8:30:14 AM
> > Subject: [PATCH] KVM: remove printing of token address
> >
> > KVM currently prints the address of the consumer token. It is not
> > immediately clear what benefit it is to see this address. Printing
> > this address leaks kernel pointers into dmesg and is a security risk.
> >
> > Remove the consumer token address from error message output.
>
> It should use %pK instead.
Is there any other way we can identify a token? There is some push back against kpt_restrict (as
used by %pK) at the moment. If there is another sane way to do it perhaps we could consider that,
else I'll use %pK for v2.
> Also, please do the same change on the VFIO
> side (drivers/vfio/pci/vfio_pci_intrs.c, call to irq_bypass_register_producer).
Oh, cool. I was wondering where the other side was. Will send v2
thanks,
Tobin.
next prev parent reply other threads:[~2017-10-09 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 6:30 [PATCH] KVM: remove printing of token address Tobin C. Harding
2017-10-09 7:49 ` Paolo Bonzini
2017-10-09 10:04 ` Tobin C. Harding [this message]
2017-10-09 10:58 ` Paolo Bonzini
2017-10-09 23:51 ` Tobin C. Harding
2017-10-10 8:31 ` Paolo Bonzini
2017-10-10 21:49 ` Tobin C. Harding
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=20171009100415.GA12785@eros \
--to=me@tobin.cc \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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