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
{{ message }}
Repository navigation
Temporarily skip test_aead_aes_gcm for buildbots with Linux kernel between 6.16.0 and 6.17.x #139310
The problem was fixed in torvalds/linux@d0ca0df because we use op.sendall(assoc, socket.MSG_MORE) just before, but socket.MSG_MORE is an even number. Because of this, af_alg_ctx.more which was previously marked as a uint32_t of 1 bit will be 0 instead because of mod 2 conversion. So the latest 6.17 kernel should not have this bug anymore.
Let's revert this in 3.16 when the branch opens, to clean the code up.
But what if someone is using an old kernel because they did not update theirs? I'm ok with keeping this guard to avoid possibly annoying reports. We already have guards for 4.9 so...
Activity
Zheaoli commentedon Sep 25, 2025
confirm it on 3.15, seems kernel change some api. Working on it
Zheaoli commentedon Sep 25, 2025
Confirm the root cause. I think it's related with this commit in the kernel torvalds/linux@1b34cbb
I'm not sure if this a bug. I'm sending a report to kernel mail group
Zheaoli commentedon Sep 25, 2025
FYI https://bugzilla.kernel.org/show_bug.cgi?id=220603
picnixz commentedon Sep 25, 2025
The previous regression was caused by how the data was actually sent. In addition, EINVAL (22) is returned by the kernel if the data is not correct (see https://docs.kernel.org/crypto/userspace-if.html#aead-cipher-api).
The problem was fixed in torvalds/linux@d0ca0df because we use
op.sendall(assoc, socket.MSG_MORE)just before, butsocket.MSG_MOREis an even number. Because of this,af_alg_ctx.morewhich was previously marked as a uint32_t of 1 bit will be 0 instead because of mod 2 conversion. So the latest 6.17 kernel should not have this bug anymore.Zheaoli commentedon Sep 25, 2025
@picnixz Yes, I think this is fixed in main branch of the kernel. I think the 6.17 will not be a issue anymore
Zheaoli commentedon Sep 30, 2025
This bug has been fixed in 6.17 release. I think this issue could be closed as resloved
hroncok commentedon Sep 30, 2025
Thanks.
30 remaining items
[3.9] gh-139310: skip `test_aead_aes_gcm` for Linux kernel between 6.…
picnixz commentedon Apr 12, 2026
@hroncok Can we revert the skip or is there some reason to keep it (and maybe refine it for exact versions?)
hroncok commentedon Apr 12, 2026
I don't know if you can revert it. In Fedora, we are likely on newer kernel already everywhere.
picnixz commentedon Apr 12, 2026
Ok, I think we can keep the guard. I don't know the exact minor version but skipping between 6.16 and 6.17 should be ok. 6.18+ have the tests enabled.
@encukou I'm going to keep the check because we are also skipping on v4.9 even if there shouldn't be lots of people on 4.9 anymore.
encukou commentedon Apr 13, 2026
Let's revert this in 3.16 when the branch opens, to clean the code up.
picnixz commentedon Apr 13, 2026
But what if someone is using an old kernel because they did not update theirs? I'm ok with keeping this guard to avoid possibly annoying reports. We already have guards for 4.9 so...
encukou commentedon May 11, 2026
When they run the CPython test suite, they get notified that a feature is missing. They can either update or skip the test themselves.
The alpha period is best for cleaning those up. (Assuming they're for bugs the kernel, not just features that didn't exist yet.)
gh-139310: Revert test skip for `test_aead_aes_gcm` (GH-139552) (GH-1…