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

auto_init: fix array-initializer order for gnrc_netdev2 stacks #6312

Merged

Conversation

miri64
Copy link
Member

@miri64 miri64 commented Jan 10, 2017

While working on #6311 I noticed, that quite a few stacks arrays for the gnrc_netdev2 auto-initialization have their initializers switched around. This leads to faulty code, since apart from a few byte all threads will have the same stack (and TCB) which leads to funny errors, like only the last initialized thread answering to IPC messages of all devices of that type.

@miri64 miri64 added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) GNRC Area: network Area: Networking labels Jan 10, 2017
@miri64 miri64 added this to the Release 2017.01 milestone Jan 10, 2017
@haukepetersen
Copy link
Contributor

could you also fix for the w5100? thx

@miri64
Copy link
Member Author

miri64 commented Jan 10, 2017

Fixed

@miri64
Copy link
Member Author

miri64 commented Jan 10, 2017

Rebased

@miri64 miri64 force-pushed the auto_init/fix/stack_array_order branch from 71d00d9 to 65e5fac Compare January 10, 2017 14:26
@OlegHahm
Copy link
Member

Nice catch!

@PeterKietzmann
Copy link
Member

Would you rebase so we can also see Jeniks working?

@PeterKietzmann PeterKietzmann added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Jan 13, 2017
@miri64 miri64 force-pushed the auto_init/fix/stack_array_order branch from 65e5fac to a4d421a Compare January 13, 2017 14:11
@miri64
Copy link
Member Author

miri64 commented Jan 13, 2017

Rebased.

@PeterKietzmann
Copy link
Member

@miri64 please squash

@miri64 miri64 force-pushed the auto_init/fix/stack_array_order branch from a4d421a to 82d8d3d Compare January 13, 2017 15:24
@miri64
Copy link
Member Author

miri64 commented Jan 13, 2017

@miri64 please squash

done

@PeterKietzmann
Copy link
Member

@haukepetersen your review was requested. Changes were addressed and Murdock/Jenkins succeeded. Pleas merge!

@miri64
Copy link
Member Author

miri64 commented Jan 17, 2017

Anyone willing to ACK?

Copy link
Contributor

@haukepetersen haukepetersen left a comment

Choose a reason for hiding this comment

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

ACK

@haukepetersen
Copy link
Contributor

and go.

@haukepetersen haukepetersen merged commit 75fabde into RIOT-OS:master Jan 17, 2017
@miri64 miri64 deleted the auto_init/fix/stack_array_order branch January 17, 2017 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: network Area: Networking CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants