Skip to content

lib: mempool: Alloc and break must happen atomically #15155

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
merged 1 commit into from
Apr 3, 2019

Conversation

pdunaj
Copy link
Collaborator

@pdunaj pdunaj commented Apr 3, 2019

This fixes a regression caused by 41e9063.

Fixes #15154

Signed-off-by: Pawel Dunaj [email protected]

This fixes a regression caused by 41e9063.

Signed-off-by: Pawel Dunaj <[email protected]>
@nashif nashif added this to the v1.14.0 milestone Apr 3, 2019
Copy link
Collaborator

@andyross andyross left a comment

Choose a reason for hiding this comment

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

Sounds right. Yeah, this is subtle.

@andrewboie andrewboie added the bug The issue is a bug, or the PR is fixing a bug label Apr 3, 2019
@andrewboie andrewboie requested a review from nashif April 3, 2019 16:32
@nashif nashif merged commit 2189d9b into zephyrproject-rtos:master Apr 3, 2019
@pdunaj
Copy link
Collaborator Author

pdunaj commented Apr 3, 2019

Hi @andyross , it probably is but this is mostly the effect of not reading carefully the comments left for future generations. Few lines above is a comment informing just about that... Thanks for quickly taking the change in.

@pdunaj pdunaj deleted the DESK-505_zephyr branch April 3, 2019 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mempool can result in OOM while memory is available
4 participants