From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Matteo Croce <mcroce@redhat.com>,
devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>,
Eric Anholt <eric@anholt.net>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH] staging: vchiq: don't leak kernel address
Date: Tue, 8 Oct 2019 17:15:47 +0200 [thread overview]
Message-ID: <20191008151547.GA2864822@kroah.com> (raw)
In-Reply-To: <20191008142517.GO21515@kadam>
On Tue, Oct 08, 2019 at 05:25:17PM +0300, Dan Carpenter wrote:
> On Tue, Oct 08, 2019 at 04:21:54PM +0200, Matteo Croce wrote:
> > On Tue, Oct 8, 2019 at 3:16 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > >
> > > The subject doesn't match the patch. It should just be "remove useless
> > > printk".
> > >
> > > regards,
> > > dan carpenter
> > >
> >
> > Well, it avoids leaking an address by removing an useless printk.
> > It seems that GKH already picked the patch in his staging tree, but
> > I'm fine with both subjects, really,
>
> The address wasn't leaked because it was already %pK. The subject
> says there is an info leak security problem, when the opposite is true.
I've edited the subject line now.
thanks,
greg k-h
prev parent reply other threads:[~2019-10-08 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 12:33 [PATCH] staging: vchiq: don't leak kernel address Matteo Croce
2019-10-08 13:15 ` Dan Carpenter
2019-10-08 14:21 ` Matteo Croce
2019-10-08 14:25 ` Dan Carpenter
2019-10-08 15:15 ` Greg Kroah-Hartman [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=20191008151547.GA2864822@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mcroce@redhat.com \
--cc=wahrenst@gmx.net \
/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