-
Notifications
You must be signed in to change notification settings - Fork 7.7k
net: buf: Disallow blocking allocation in syswq #71697
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
net: buf: Disallow blocking allocation in syswq #71697
Conversation
94de455
to
a280b3a
Compare
@jori-nordic CI is failing due to a misspelled word. The change itself looks fine to me. |
a280b3a
to
b34f994
Compare
@jhedberg fixed, thanks |
@@ -1315,14 +1315,19 @@ int net_buf_id(struct net_buf *buf); | |||
/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit, we usually have net:
prefix instead of "networking" in commit subject that are related to networking files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it, fixed 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah shoot looks like the CI re-runs when you only update the commit message. @stephanosio do you think we could make it so we only run the compliance in those cases?
Work items on the syswq should always run-to-completion. Override the timeout value to always be K_NO_WAIT. Allocating with K_FOREVER leads to deadlocks if the freeing also happens from the syswq. Non-zero timeouts are also not nice for the other users of the syswq. Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
b34f994
to
d4d5301
Compare
Work items on the syswq should always run-to-completion.
Override the timeout value to always be K_NO_WAIT.
Allocating with K_FOREVER leads to deadlocks if the freeing also happens from the syswq. Non-zero timeouts are also not nice for the other users of the syswq.