You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an internal test which triggers a health event and checks for techsupport. Triggering a health event causes dockers to restart.
Very rarely (Only twice until now) during docker stop, we observed a RCU stall on the CPU. Looks like some user space process is removing a network namespace which is triggering the cleanup_net tasklet, which gets stuck in the devlinks_xa_find_get function.
This is also reported in the syzkaller multiple times in the linux 6.1.y branch during syzkaller fuzzy testing. https://syzkaller.appspot.com/bug?extid=e361cbd0ce11d6558816. Crash reported there is also on devlinks_xa_find_get during cleanup_net tasklet
Description
We have an internal test which triggers a health event and checks for techsupport. Triggering a health event causes dockers to restart.
Very rarely (Only twice until now) during docker stop, we observed a RCU stall on the CPU. Looks like some user space process is removing a network namespace which is triggering the cleanup_net tasklet, which gets stuck in the devlinks_xa_find_get function.
This is also reported in the syzkaller multiple times in the linux 6.1.y branch during syzkaller fuzzy testing. https://syzkaller.appspot.com/bug?extid=e361cbd0ce11d6558816. Crash reported there is also on devlinks_xa_find_get during cleanup_net tasklet
The text was updated successfully, but these errors were encountered: