* Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614)
@ 2021-04-07 1:20 Jack Hill
2021-04-07 1:38 ` Philip McGrath
0 siblings, 1 reply; 2+ messages in thread
From: Jack Hill @ 2021-04-07 1:20 UTC (permalink / raw)
To: Mark H Weaver; +Cc: guix-devel
On Tue, 6 Apr 2021, Mark H Weaver wrote:
> Anyway, I doubt that imposing such a limitation would adequately solve
> the problem here of chunked references in Racket 8, because I suspect
> that Racket 8 could split store references at arbitrary points in the
> string. I doubt that we can safely assume that the hash component of
> store references will be stored contiguously in *.zo files.
Mark and everyone,
I wanted to spin off a subthread on guix-devel, to make you aware of
another problem that we've run into with reference in .zo getting mangled:
https://issues.guix.gnu.org/47180
Best,
Jack
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614)
2021-04-07 1:20 Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614) Jack Hill
@ 2021-04-07 1:38 ` Philip McGrath
0 siblings, 0 replies; 2+ messages in thread
From: Philip McGrath @ 2021-04-07 1:38 UTC (permalink / raw)
To: Jack Hill, Mark H Weaver; +Cc: guix-devel
Indeed, I expect this is a more precise diagnosis of the same problem.
My patch in https://issues.guix.gnu.org/47180 solves it by putting the
store references (search paths for foreign libraries) in a configuration
data file that isn't compiled, so they don't end up in .zo files in the
first place.
The .zo format is intentionally undocumented and subject to breaking
change, including from different compilation options. At a minimum, a
change to the Racket version number signals a breaking change to
compiled code (e.g. Git is now at 8.0.0.13, so 13 breaking changes since
the release). Internally, I don't know all the details, but the normal
8.0 .zo format has a Racket layer around the Chez Scheme object format,
which seems to be very complex: it looks like it supports
user-configurable compression at the granularity of the individual
object within an object file. So it seems much better to avoid rewriting
.zo files altogether.
-Philip
On 4/6/21 9:20 PM, Jack Hill wrote:
> On Tue, 6 Apr 2021, Mark H Weaver wrote:
>
>> Anyway, I doubt that imposing such a limitation would adequately solve
>> the problem here of chunked references in Racket 8, because I suspect
>> that Racket 8 could split store references at arbitrary points in the
>> string. I doubt that we can safely assume that the hash component of
>> store references will be stored contiguously in *.zo files.
>
> Mark and everyone,
>
> I wanted to spin off a subthread on guix-devel, to make you aware of
> another problem that we've run into with reference in .zo getting
> mangled: https://issues.guix.gnu.org/47180
>
> Best,
> Jack
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-04-07 12:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-07 1:20 Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614) Jack Hill
2021-04-07 1:38 ` Philip McGrath
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).