Linux CAN drivers development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: [can-next v2] can: proc: remove pointers from CAN specific proc output
Date: Thu, 20 Aug 2026 16:27:34 +0200	[thread overview]
Message-ID: <20260820142734.NuRnRMV9@linutronix.de> (raw)
In-Reply-To: <20260815103400.117175-1-socketcan@hartkopp.net>

On 2026-08-15 12:34:00 [+0200], Oliver Hartkopp wrote:
> The proc content in /proc/net/can/ and /proc/net/can-bcm/ is intended to
> check the internal filter lists (af_can, can_raw) and the efficiency and
> functionality of can_bcm jobs. While it was ok to leak kernel internal
> addresses at time of writing the times have changed and multiple attempts
> have been taken to hash or remove such now sensible data.
> 
> This patch removes the disclosure of pointers and instead provides the
> function names and sock inode numbers when available. As there's no known
> tooling around the CAN specific proc output breaking the ABI with this
> rework creates no issue.
> 
> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>

Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

Sebastian

      reply	other threads:[~2026-08-20 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 10:34 [can-next v2] can: proc: remove pointers from CAN specific proc output Oliver Hartkopp
2026-08-20 14:27 ` Sebastian Andrzej Siewior [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=20260820142734.NuRnRMV9@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.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