Stream: git-wasmtime

Topic: wasmtime / issue #4813 feat: add a knob for reset stack


view this post on Zulip Wasmtime GitHub notifications bot (Aug 30 2022 at 03:42):

github-actions[bot] commented on issue #4813:

Subscribe to Label Action

cc @peterhuene

<details>
This issue or pull request has been labeled: "wasmtime:api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Aug 30 2022 at 03:42):

github-actions[bot] commented on issue #4813:

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html


<details>

To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.

To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.

Learn more.

</details>

view this post on Zulip Wasmtime GitHub notifications bot (Aug 30 2022 at 15:45):

cfallin commented on issue #4813:

Actually though as I think more about this, I feel that there's a case to be made for removing this option entirely and simply not resetting stack pages back to zero. I don't think that the defense-in-depth argument holds a ton of water here because we make no attempt to reset the stack for non-async calls. If an alternate stack was always used then I think there's a case to be made for having this as an option since it would be turning off a uniformly off-by-default behavior, but otherwise as-is this option is only applicable with async support and the pooling instance allocator, both of which are already niche.

@cfallin I know in the past you've argued that this behavior should remain, so I'm curious if you still feel that way or if I could perhaps convince you of otherwise.

I think it's pretty important to keep this behavior, for a few reasons:

view this post on Zulip Wasmtime GitHub notifications bot (Aug 30 2022 at 16:56):

alexcrichton commented on issue #4813:

That sounds reasonable to me. @Duslia would you be ok implementing this new option, but flipping the defaults? Instead the option would enable the zeroing behavior that is currently the default today, and by default Wasmtime wouldn't zero stacks async stacks.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 01 2022 at 15:27):

alexcrichton commented on issue #4813:

I pushed up some tweaks to the wording here but otherwise this looks good to me, thanks!


Last updated: Dec 23 2024 at 12:05 UTC