rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geoffrey Thomas <geofft@ldpreload.com>
To: se iro <seiro22@mailfence.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: leaky info and kernel modules
Date: Wed, 7 Apr 2021 12:50:30 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.2104071235550.11174@titan.ldpreload.com> (raw)
In-Reply-To: <1802230489.25122.1617805363569@ichabod.co-bxl>

On Wed, 7 Apr 2021, se iro wrote:

> saw post on reddit and github issues where rust compiler adds username 
> and systems paths/info to **release** mode compile bins. also its pkg 
> mgr cargo does the same with registry paths. otherwise its extra strings 
> bloating output that not needed and strip command doesnt work. also not 
> working is compiler opts described

I think what's going on is that, while this is unusual for most dynamic 
languages (and the Rust language intentionally targets the community of 
users of dynamic languages), it's actually the normal behavior for 
compiled languages - compiled C binaries include full paths in their 
debuginfo too. I checked a random released kernel that I'm running, and it 
has full source file paths (including the username, if you built in /home) 
in its debug info, so for the purposes of Rust in the Linux kernel, I 
don't think this is an effective change.

We should definitely match what the rest of the kernel does in terms of 
debug info, but I think we already do.

-- 
Geoffrey Thomas
https://ldpreload.com
geofft@ldpreload.com

  reply	other threads:[~2021-04-07 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 14:22 leaky info and kernel modules se iro
2021-04-07 16:50 ` Geoffrey Thomas [this message]
2021-04-07 21:50 ` Miguel Ojeda
2021-04-07 22:12   ` Miguel Ojeda
2021-04-08  2:38   ` se iro
2021-04-08  6:35     ` Miguel Ojeda

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=alpine.DEB.2.11.2104071235550.11174@titan.ldpreload.com \
    --to=geofft@ldpreload.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=seiro22@mailfence.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).