-
Notifications
You must be signed in to change notification settings - Fork 2k
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
sys/xtimer: _xtimer_now64(): fix irq_disable() return value type #13182
Conversation
Nice catch @kaspar030 ! |
Tested on
-pr
|
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.
ACK! Thanks for investigating this and providing the fix @kaspar030, I'll run all tests on hifive1b ass good measure, but the fix is obvious.
I'll use the results in #13086 as a comparison point. |
GO!, still waiting on all tests results but the change is valid on its own. |
Backport provided in #13183 |
Nice catch @kaspar030, thanks! |
As a reminder for our offline discussion: maybe having a Coccinelle check for that in the CI is a good idea. |
Re0ran the tests on
|
Contribution description
Small mistake, large impact. Use of the wrong type for the return value of
irq_disable()
basically chopped off part of the ISR state.On the fe310, this lead to a trap right after xtimer ISR exit, sometimes.
Testing procedure
Fix should be obvious.
Issues/PRs references
Fixes #13109.