Skip to content

Conversation

@glpesk
Copy link
Collaborator

@glpesk glpesk commented Jun 19, 2025

Recently, some subcommands of ffx have been split into separate binaries, and others depend on prebuilt artifacts. This PR updates the Starnix VM startup script to get the current path for each artifact (either from the default ffx config or from the tool manifest), and refactors the ffx helpers to make the call sites more consistent.

(Starnix bug ref: this is a fix for https://fxbug.dev/409390594.)

@glpesk glpesk force-pushed the syzkallnix branch 2 times, most recently from 85cc7cf to 634b89c Compare June 19, 2025 00:26
@glpesk glpesk requested a review from eepeep June 19, 2025 00:38
Copy link
Collaborator

@eepeep eepeep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to take a bit to get back to you on this! Generally seems good to me, assuming that this is the approach recommended by the ffx team, with a couple nits for readability. Thank you for fixing this!

@glpesk glpesk force-pushed the syzkallnix branch 2 times, most recently from 4d8d91e to b06846c Compare July 2, 2025 23:17
glpesk added 2 commits July 22, 2025 14:51
ffx emu now needs to know the locations of some host
tools. Copy these paths from the default ffx config
into the configuration for the isolated ffx instance
that syzkaller uses for most tasks.
ffx log is now built separately from the main
ffx binary.
@glpesk glpesk enabled auto-merge July 22, 2025 22:04
@glpesk glpesk added this pull request to the merge queue Jul 22, 2025
Merged via the queue into google:master with commit e1dd4f2 Jul 22, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants