All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, saeedm@nvidia.com,
	leon@kernel.org, tariqt@nvidia.com, mbloch@nvidia.com,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	aleksandr.loktionov@intel.com, horms@kernel.org,
	pmenzel@molgen.mpg.de
Subject: Re: [Intel-wired-lan] [PATCH net-next v5 0/2] net: Don't use %pK through printk or tracepoints
Date: Thu, 14 Aug 2025 01:30:17 +0000	[thread overview]
Message-ID: <175513501748.3846704.2653284504088460874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250811-restricted-pointers-net-v5-0-2e2fdc7d3f2c@linutronix.de>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 11 Aug 2025 11:43:17 +0200 you wrote:
> In the past %pK was preferable to %p as it would not leak raw pointer
> values into the kernel log.
> Since commit ad67b74d2469 ("printk: hash addresses printed with %p")
> the regular %p has been improved to avoid this issue.
> Furthermore, restricted pointers ("%pK") were never meant to be used
> through printk(). They can still unintentionally leak raw pointers or
> acquire sleeping locks in atomic contexts.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/2] ice: Don't use %pK through printk or tracepoints
    https://git.kernel.org/netdev/net-next/c/66ceb45b7d7e
  - [net-next,v5,2/2] net/mlx5: Don't use %pK through tracepoints
    https://git.kernel.org/netdev/net-next/c/e2068f74b976

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, saeedm@nvidia.com,
	leon@kernel.org, tariqt@nvidia.com, mbloch@nvidia.com,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	aleksandr.loktionov@intel.com, horms@kernel.org,
	pmenzel@molgen.mpg.de
Subject: Re: [PATCH net-next v5 0/2] net: Don't use %pK through printk or tracepoints
Date: Thu, 14 Aug 2025 01:30:17 +0000	[thread overview]
Message-ID: <175513501748.3846704.2653284504088460874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250811-restricted-pointers-net-v5-0-2e2fdc7d3f2c@linutronix.de>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 11 Aug 2025 11:43:17 +0200 you wrote:
> In the past %pK was preferable to %p as it would not leak raw pointer
> values into the kernel log.
> Since commit ad67b74d2469 ("printk: hash addresses printed with %p")
> the regular %p has been improved to avoid this issue.
> Furthermore, restricted pointers ("%pK") were never meant to be used
> through printk(). They can still unintentionally leak raw pointers or
> acquire sleeping locks in atomic contexts.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/2] ice: Don't use %pK through printk or tracepoints
    https://git.kernel.org/netdev/net-next/c/66ceb45b7d7e
  - [net-next,v5,2/2] net/mlx5: Don't use %pK through tracepoints
    https://git.kernel.org/netdev/net-next/c/e2068f74b976

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-08-14  1:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11  9:43 [Intel-wired-lan] [PATCH net-next v5 0/2] net: Don't use %pK through printk or tracepoints Thomas Weißschuh
2025-08-11  9:43 ` Thomas Weißschuh
2025-08-11  9:43 ` [Intel-wired-lan] [PATCH net-next v5 1/2] ice: " Thomas Weißschuh
2025-08-11  9:43   ` Thomas Weißschuh
2025-08-11  9:43 ` [Intel-wired-lan] [PATCH net-next v5 2/2] net/mlx5: Don't use %pK through tracepoints Thomas Weißschuh
2025-08-11  9:43   ` Thomas Weißschuh
2025-08-11 23:59 ` [Intel-wired-lan] [PATCH net-next v5 0/2] net: Don't use %pK through printk or tracepoints Jacob Keller
2025-08-11 23:59   ` Jacob Keller
2025-08-14  1:30 ` patchwork-bot+netdevbpf [this message]
2025-08-14  1:30   ` patchwork-bot+netdevbpf

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=175513501748.3846704.2653284504088460874.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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.