[v3.7] mDNS reponder might fail to serve if mDNS resolver is enabled #78146
Assignees
Labels
area: Networking
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Milestone
Comments
jukkar
added
bug
jukkar
added a commit
to jukkar/zephyr
that referenced
this issue
Sep 9, 2024
The socket services API has a limitation where the user data is shared between file descriptors described in the same service. This can cause problem in DNS dispatcher where each listened socket needs to have their own dispatcher struct set as user data so that we can map between dispatcher context and socket. Solve this by always have a dispatcher table as user data, and then have the actual mapping done via the dispatcher table when receiving data to the dispatcher socket. Fixes zephyrproject-rtos#78146 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
This was referenced Sep 9, 2024
zephyrbot
pushed a commit
that referenced
this issue
Sep 11, 2024
The socket services API has a limitation where the user data is shared between file descriptors described in the same service. This can cause problem in DNS dispatcher where each listened socket needs to have their own dispatcher struct set as user data so that we can map between dispatcher context and socket. Solve this by always have a dispatcher table as user data, and then have the actual mapping done via the dispatcher table when receiving data to the dispatcher socket. Fixes #78146 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no> (cherry picked from commit caf9fd3)
kartben
pushed a commit
to kartben/zephyr
that referenced
this issue
Sep 11, 2024
The socket services API has a limitation where the user data is shared between file descriptors described in the same service. This can cause problem in DNS dispatcher where each listened socket needs to have their own dispatcher struct set as user data so that we can map between dispatcher context and socket. Solve this by always have a dispatcher table as user data, and then have the actual mapping done via the dispatcher table when receiving data to the dispatcher socket. Fixes zephyrproject-rtos#78146 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
nagelkl
pushed a commit
to nagelkl/zephyr
that referenced
this issue
Sep 16, 2024
The socket services API has a limitation where the user data is shared between file descriptors described in the same service. This can cause problem in DNS dispatcher where each listened socket needs to have their own dispatcher struct set as user data so that we can map between dispatcher context and socket. Solve this by always have a dispatcher table as user data, and then have the actual mapping done via the dispatcher table when receiving data to the dispatcher socket. Fixes zephyrproject-rtos#78146 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
nashif
pushed a commit
that referenced
this issue
Sep 23, 2024
The socket services API has a limitation where the user data is shared between file descriptors described in the same service. This can cause problem in DNS dispatcher where each listened socket needs to have their own dispatcher struct set as user data so that we can map between dispatcher context and socket. Solve this by always have a dispatcher table as user data, and then have the actual mapping done via the dispatcher table when receiving data to the dispatcher socket. Fixes #78146 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no> (cherry picked from commit caf9fd3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depending on number of services configured and if the DNS dispatcher is active, so both responder and resolver are enabled at the same time, the mDNS responder might not get any queries.
This issue is created for backporting 3.7 purposes.
The text was updated successfully, but these errors were encountered: