From: Greg KH <gregkh@linuxfoundation.org>
To: Todd Kjos <tkjos@android.com>
Cc: devel@driverdev.osuosl.org, arve@android.com, maco@google.com,
linux-kernel@vger.kernel.org, tkjos@google.com
Subject: Re: [PATCH] binder: replace "%p" with "%pK"
Date: Wed, 7 Feb 2018 16:56:28 -0600 [thread overview]
Message-ID: <20180207225628.GC10647@kroah.com> (raw)
In-Reply-To: <20180207215737.251082-1-tkjos@google.com>
On Wed, Feb 07, 2018 at 01:57:37PM -0800, Todd Kjos wrote:
> The format specifier "%p" can leak kernel addresses. Use
> "%pK" instead. There were 4 remaining cases in binder.c.
Luckily this isn't an issue in mainline as we don't print %p values out
anymore as of 4.15. That being said, this is a good fix and I'll queue
it up after 4.16-rc1 is out, thanks.
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2018-02-07 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:57 [PATCH] binder: replace "%p" with "%pK" Todd Kjos
2018-02-07 22:56 ` Greg KH [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=20180207225628.GC10647@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@google.com \
--cc=tkjos@android.com \
--cc=tkjos@google.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