archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <>
To: se iro <>
Subject: Re: leaky info and kernel modules
Date: Thu, 8 Apr 2021 08:35:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Se Iro,

On Thu, Apr 8, 2021 at 4:38 AM se iro <> wrote:
> you mention debug but this is building release mode not debug which is why it odd.

I was talking about release mode (please note I said "without"
`DEBUG_KERNEL`, not "with"). Perhaps I misunderstood you?

> and yeah if these paths exists its not reproducible as they different for everyone else. steve k commented on reddit and said he thinks so long as build process is same its reproducible, not that hashing matching is require. rust team may have differ opinion on what reproducible builds are too which affect this like you say

Reproducible builds are, in the end, about achieving the same output
every time. How to achieve that, however, can be easier or harder
depending on how much state/environment a project relies upon.

So, for instance, if we have absolute paths in the binary, then that
is one more thing to worry when preparing the build. That is why
removing the paths improves reproducibility, but it is not the only
thing that is required to achieve it for the kernel (i.e. we are not
breaking reproducibility just because we have those paths & one can
still achieve it by taking care of the paths).


      reply	other threads:[~2021-04-08  6:35 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
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 [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).