All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-staging@lists.linux.dev,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Dan Carpenter <error27@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH v2 0/2] staging: vc04_services: Use %p to log pointer
Date: Mon, 4 Dec 2023 08:08:27 +0100	[thread overview]
Message-ID: <2023120459-irregular-cost-1785@gregkh> (raw)
In-Reply-To: <20231128202007.489294-1-umang.jain@ideasonboard.com>

On Wed, Nov 29, 2023 at 01:50:05AM +0530, Umang Jain wrote:
> %lx is used to print the unmodified pointer address for debugging.
> %p will print the hashed pointer address to avoid leaking information
> about kernel memory layout to userspace. But when `no_hash_pointers`
> is passed as kernel parameter, unmodified pointer address will be
> printed.
> 
> Hence, drop %lx in favour of %p. For debugging purposes, one can
> easily depend on `no_hash_pointers`.
> 
> This also solves the following smatch warnings:
> service_callback() warn: argument 7 to %lx specifier is cast from pointer
> service_callback() warn: argument 11 to %lx specifier is cast from pointer
> service_callback() warn: argument 12 to %lx specifier is cast from pointer
> service_callback() warn: argument 13 to %lx specifier is cast from pointer
> vchiq_release() warn: argument 7 to %lx specifier is cast from pointer
> 
> Changes in v2:
> - Built/Rebased on top of:
>   [PATCH v2 0/5] staging: vc04_services: Drop custom logging
> 
> Umang Jain (2):
>   staging: vc04_services: Use %p to log pointer address
>   staging: vc04_services: Use %p to log pointer address

You have 2 different patches that do different things, yet have the
identical subject lines.  That needs to be fixed up before I can take
them.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-staging@lists.linux.dev,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Dan Carpenter <error27@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH v2 0/2] staging: vc04_services: Use %p to log pointer
Date: Mon, 4 Dec 2023 08:08:27 +0100	[thread overview]
Message-ID: <2023120459-irregular-cost-1785@gregkh> (raw)
In-Reply-To: <20231128202007.489294-1-umang.jain@ideasonboard.com>

On Wed, Nov 29, 2023 at 01:50:05AM +0530, Umang Jain wrote:
> %lx is used to print the unmodified pointer address for debugging.
> %p will print the hashed pointer address to avoid leaking information
> about kernel memory layout to userspace. But when `no_hash_pointers`
> is passed as kernel parameter, unmodified pointer address will be
> printed.
> 
> Hence, drop %lx in favour of %p. For debugging purposes, one can
> easily depend on `no_hash_pointers`.
> 
> This also solves the following smatch warnings:
> service_callback() warn: argument 7 to %lx specifier is cast from pointer
> service_callback() warn: argument 11 to %lx specifier is cast from pointer
> service_callback() warn: argument 12 to %lx specifier is cast from pointer
> service_callback() warn: argument 13 to %lx specifier is cast from pointer
> vchiq_release() warn: argument 7 to %lx specifier is cast from pointer
> 
> Changes in v2:
> - Built/Rebased on top of:
>   [PATCH v2 0/5] staging: vc04_services: Drop custom logging
> 
> Umang Jain (2):
>   staging: vc04_services: Use %p to log pointer address
>   staging: vc04_services: Use %p to log pointer address

You have 2 different patches that do different things, yet have the
identical subject lines.  That needs to be fixed up before I can take
them.

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-12-04 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 20:20 [PATCH v2 0/2] staging: vc04_services: Use %p to log pointer Umang Jain
2023-11-28 20:20 ` Umang Jain
2023-11-28 20:20 ` [PATCH v2 1/2] staging: vc04_services: Use %p to log pointer address Umang Jain
2023-11-28 20:20   ` Umang Jain
2023-12-04  7:07   ` Greg Kroah-Hartman
2023-12-04  7:07     ` Greg Kroah-Hartman
2023-11-28 20:20 ` [PATCH v2 2/2] " Umang Jain
2023-11-28 20:20   ` Umang Jain
2023-12-04  7:08 ` Greg Kroah-Hartman [this message]
2023-12-04  7:08   ` [PATCH v2 0/2] staging: vc04_services: Use %p to log pointer Greg Kroah-Hartman

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=2023120459-irregular-cost-1785@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=error27@gmail.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=ricardo@marliere.net \
    --cc=stefan.wahren@i2se.com \
    --cc=umang.jain@ideasonboard.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.