Skip to content

Net services should start after the stack is fully ready #15141

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 2 commits into from
Apr 3, 2019

Conversation

tbursztyka
Copy link
Collaborator

@tbursztyka tbursztyka commented Apr 3, 2019

Fixing net "servicing" starting order.

Fixes #15124

Tomasz Bursztyka added 2 commits April 3, 2019 09:03
Just provide a macro of value 0 in case CONFIG_NET_DHCPV4 is unset.

Signed-off-by: Tomasz Bursztyka <[email protected]>
DNS is not part of L3, but as dhcpv4 or the net shell, it is a services
on top of the network stack. So let's gather all in a dedicated
function.

This also rework the order when starting the DNS service. There was an
issue for offload device: these would be fully initialized in
init_rx_queues() which was called after l3_init. l3_init had already
started dns: which would not be able to bind correctly, proving to be
fully dead afterwards. Instead, starting the dns at the very end
ensures that all is initialized properly from devices to stack.

Fixes zephyrproject-rtos#15124

Signed-off-by: Tomasz Bursztyka <[email protected]>
@tbursztyka tbursztyka added bug The issue is a bug, or the PR is fixing a bug area: Networking labels Apr 3, 2019
@tbursztyka tbursztyka requested a review from pfalcon as a code owner April 3, 2019 07:18
@jukkar jukkar added the priority: low Low impact/importance bug label Apr 3, 2019
@jukkar jukkar added this to the v1.14.0 milestone Apr 3, 2019
@nashif nashif merged commit 16dd53b into zephyrproject-rtos:master Apr 3, 2019
@tbursztyka tbursztyka deleted the dns_offload branch May 8, 2019 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants