-
Notifications
You must be signed in to change notification settings - Fork 104
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
Rework tail_lock to provide it usability in kernel code. #1859
Comments
We discussed that the |
EvgeniiMekhanik
added a commit
that referenced
this issue
May 30, 2023
After fix `tail_lock` usage in kernel code remove all `tail_lock` hotfix code. Closes #1859
EvgeniiMekhanik
added a commit
that referenced
this issue
May 30, 2023
After fix `tail_lock` usage in kernel code remove all `tail_lock` hotfix code. Closes #1859
EvgeniiMekhanik
added a commit
that referenced
this issue
May 30, 2023
After fix `tail_lock` usage in kernel code remove all `tail_lock` hotfix code. Closes #1859
EvgeniiMekhanik
added a commit
that referenced
this issue
Jun 5, 2023
After fix `tail_lock` usage in kernel code remove all `tail_lock` hotfix code. Closes #1859
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
Currently if tail_lock is set when skb is passed to kernel code, BUG_ON is fire. We should rework tail_lock or appropriate functions in kernel code. They should work with skb with tail_lock
The text was updated successfully, but these errors were encountered: