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

Fix LB halo communication #4078

Merged
merged 6 commits into from
Jan 8, 2021
Merged

Conversation

jngrad
Copy link
Member

@jngrad jngrad commented Dec 29, 2020

Fixes #4077

Description of changes:

  • improve testing of halo communication
  • fix undefined behavior in halo communication
  • fix mixed type expressions flagged as alerts by LGTM

Check one-way halo communication (HALO_RECV, HALO_SEND, HALO_OPEN)
using open boundaries (that are blocked by a LBBoundary).
Function no longer used since 42dffbc
Fields no longer used since 7b1a2b9
For LB grids of size 9x9x9 or larger, the product `vstride * extent`
can overflow. UBSAN report: signed integer overflow: 25920 * 492408
cannot be represented in type 'int'.
Don't mix signed with unsigned types. Avoid int overflow.
@reinaual reinaual added the automerge Merge with kodiak label Jan 8, 2021
@kodiakhq kodiakhq bot merged commit 74899cd into espressomd:python Jan 8, 2021
@jngrad jngrad deleted the halo_comm_bugfix branch January 8, 2021 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Undefined behavior in LB halo communication
2 participants