From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Zhiwei Yang <yangzhiwei@uniontech.com>
Cc: Felipe Balbi <balbi@kernel.org>, linux-usb@vger.kernel.org
Subject: Re: [PATCH] USB: phy: tahvo:replace "%p" with "%pK"
Date: Fri, 24 Sep 2021 10:19:33 +0200 [thread overview]
Message-ID: <YU2KFcOWBWU3UsZV@kroah.com> (raw)
In-Reply-To: <20210924075913.31584-1-yangzhiwei@uniontech.com>
On Fri, Sep 24, 2021 at 03:59:13PM +0800, Zhiwei Yang wrote:
> Use "%pK" to avoid kernel address leaked
>
> Signed-off-by: Zhiwei Yang <yangzhiwei@uniontech.com>
> ---
> drivers/usb/phy/phy-tahvo.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/phy/phy-tahvo.c b/drivers/usb/phy/phy-tahvo.c
> index baebb1f5a973..5dc600fadc5f 100644
> --- a/drivers/usb/phy/phy-tahvo.c
> +++ b/drivers/usb/phy/phy-tahvo.c
> @@ -194,7 +194,7 @@ static int tahvo_usb_set_host(struct usb_otg *otg, struct usb_bus *host)
> struct tahvo_usb *tu = container_of(otg->usb_phy, struct tahvo_usb,
> phy);
>
> - dev_dbg(&tu->pt_dev->dev, "%s %p\n", __func__, host);
> + dev_dbg(&tu->pt_dev->dev, "%s %pK\n", __func__, host);
>
> mutex_lock(&tu->serialize);
>
> @@ -224,7 +224,7 @@ static int tahvo_usb_set_peripheral(struct usb_otg *otg,
> struct tahvo_usb *tu = container_of(otg->usb_phy, struct tahvo_usb,
> phy);
>
> - dev_dbg(&tu->pt_dev->dev, "%s %p\n", __func__, gadget);
> + dev_dbg(&tu->pt_dev->dev, "%s %pK\n", __func__, gadget);
>
> mutex_lock(&tu->serialize);
>
> --
> 2.20.1
>
>
>
Both of these lines should just be removed as ftrace can be (and should
be) used instead for stuff like "did the kernel get to this function?"
that these lines seem to be for.
So can you just resubmit this as removing those lines?
thanks,
greg k-h
parent reply other threads:[~2021-09-24 8:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210924075913.31584-1-yangzhiwei@uniontech.com>]
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=YU2KFcOWBWU3UsZV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yangzhiwei@uniontech.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 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.