Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Merged by Bors] - Fix unsoundness in EntityMut::world_scope #7387

Closed
wants to merge 17 commits into from
Closed
Changes from 16 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 42 additions & 3 deletions crates/bevy_ecs/src/world/entity_ref.rs
Original file line number Diff line number Diff line change
Expand Up @@ -564,9 +564,22 @@ impl<'w> EntityMut<'w> {
/// # assert_eq!(new_r.0, 1);
/// ```
pub fn world_scope<U>(&mut self, f: impl FnOnce(&mut World) -> U) -> U {
let val = f(self.world);
self.update_location();
val
struct Guard<'w, 'a> {
entity_mut: &'a mut EntityMut<'w>,
}

impl Drop for Guard<'_, '_> {
#[inline]
fn drop(&mut self) {
self.entity_mut.update_location();
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we document that world_scope() calls update_location()? This was missing in the original code too.

Copy link
Contributor

Choose a reason for hiding this comment

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

This was a conscious choice not to mention unsafe implementation details in the docs of a safe method

Copy link
Contributor

@djeedai djeedai Jan 28, 2023

Choose a reason for hiding this comment

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

Fair. But on the other hand if I see the update_location() on docs.rs then I will immediately ask myself "should I use that after world_scope()?", and safety doesn't answer my question; if anything I'd be tempted to think I do need it since it's unsafe but world_scope() is not.

Copy link
Member Author

Choose a reason for hiding this comment

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

The docs for EntityMut::update_location say that it only needs to be called if you are using EntityMut::world_mut. Perhaps it could be phrased differently to make that more clear?

Copy link
Contributor

Choose a reason for hiding this comment

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

Then that should be fine.

}
}

// When `guard` is dropped at the end of this scope,
// it will update the cached `EntityLocation` for this instance.
// This will run even in case the closure `f` unwinds.
let guard = Guard { entity_mut: self };
f(guard.entity_mut.world)
}

/// Updates the internal entity location to match the current location in the internal
Expand Down Expand Up @@ -856,6 +869,8 @@ pub(crate) unsafe fn take_component<'a>(

#[cfg(test)]
mod tests {
use std::panic::AssertUnwindSafe;

use crate as bevy_ecs;
use crate::component::ComponentId;
use crate::prelude::*; // for the `#[derive(Component)]`
Expand Down Expand Up @@ -947,4 +962,28 @@ mod tests {
assert!(entity.get_by_id(invalid_component_id).is_none());
assert!(entity.get_mut_by_id(invalid_component_id).is_none());
}

// regression test for https://github.com/bevyengine/bevy/pull/7387
#[test]
JoJoJet marked this conversation as resolved.
Show resolved Hide resolved
fn entity_mut_world_scope_panic() {
let mut world = World::new();

let mut entity = world.spawn_empty();
let old_location = entity.location();
let id = entity.id();
let res = std::panic::catch_unwind(AssertUnwindSafe(|| {
Copy link
Member

Choose a reason for hiding this comment

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

Do you need the AssertUnwindSafe by making the closure move?

Copy link
Member Author

Choose a reason for hiding this comment

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

This would move the variable entity into the closure and make it inaccessible to the rest of the test.

entity.world_scope(|w| {
// Change the entity's `EntityLocation`, which invalidates the original `EntityMut`.
// This will get updated at the end of the scope.
w.entity_mut(id).insert(TestComponent(0));

// Ensure that the entity location still gets updated even in case of a panic.
panic!("this should get caught by the outer scope")
});
}));
assert!(res.is_err());

// Ensure that the location has been properly updated.
assert!(entity.location() != old_location);
}
}