In the --developer build, there is a panic due to talloc stack frames not freed in order when setting an acl via the acl_xattr module (or acl_tdb) fails with ACCESS_DENIED. One way to reproduce: - configure.developer ... - build without posix acl support (I did it by accident) - configure a share with vfs_acl_xattr enabled (vfs objects = acl_xattr) - crate a file in that share - add an ace to the acl of the file => this failed with access denied due to "to many aces to map to posix perms" => error code path in vfs_acl_common does not free frame => main event loop panics "frame not freed in order" This is a panic only in developer builds. Michael
Created attachment 8273 [details] patch for v4-0-test Patch as cherry-picked from master
Comment on attachment 8273 [details] patch for v4-0-test Looks good
Pushed to autobuild-v4-0-test.
Pushed to v4-0-test. Closing out bug report. Thanks!