Can you share also the updated config-files for i686 and x86_64?
They are no longer working from our current kernel. Furthermore: The patches for rxrpc are not applied. So they need rework.
I share them here:
rxrpc-also-unshare-DATA-RESPONSE-packets-when-paged.patch
--- a/net/rxrpc/conn_event.c
+++ b/net/rxrpc/conn_event.c
@@ -291,7 +291,7 @@ static int rxrpc_verify_response(struct rxrpc_connection *conn,
{
int ret;
- if (skb_cloned(skb)) {
+ if (skb_cloned(skb) || skb_is_nonlinear(skb)) {
/* Copy the packet if shared so that we can do in-place
* decryption.
*/
--- a/net/rxrpc/input.c 2026-05-21 01:06:23.176288938 +0200
+++ b/net/rxrpc/input.c 2026-05-21 01:07:21.406104131 +0200
@@ -1287,7 +1287,7 @@
* decryption.
*/
if (sp->hdr.securityIndex != 0 &&
- skb_cloned(skb)) {
+ (skb_cloned(skb) || skb_is_nonlinear(skb))) {
struct sk_buff *nskb = skb_copy(skb, GFP_ATOMIC);
if (!nskb) {
kfree_skb(skb);
rxrpc-fix-conn-level-packet-handling-to-unshare-RESP.patch
--- a/net/rxrpc/conn_event.c 2026-05-21 01:03:09.676903055 +0200
+++ b/net/rxrpc/conn_event.c 2026-05-21 01:03:59.736744177 +0200
@@ -285,6 +285,35 @@
}
}
+static int rxrpc_verify_response(struct rxrpc_connection *conn,
+ struct sk_buff *skb,
+ u32 *_abort_code)
+{
+ int ret;
+
+ if (skb_cloned(skb)) {
+ /* Copy the packet if shared so that we can do in-place
+ * decryption.
+ */
+ struct sk_buff *nskb = skb_copy(skb, GFP_NOFS);
+
+ if (nskb) {
+ rxrpc_new_skb(nskb, rxrpc_skb_unshared);
+ ret = conn->security->verify_response(conn, nskb,
+ _abort_code);
+ rxrpc_free_skb(nskb, rxrpc_skb_freed);
+ } else {
+ /* OOM - Drop the packet. */
+ rxrpc_see_skb(skb, rxrpc_skb_unshared_nomem);
+ ret = -ENOMEM;
+ }
+ } else {
+ ret = conn->security->verify_response(conn, skb, _abort_code);
+ }
+
+ return ret;
+}
+
/*
* connection-level Rx packet processor
*/
@@ -337,7 +366,7 @@
_abort_code);
case RXRPC_PACKET_TYPE_RESPONSE:
- ret = conn->security->verify_response(conn, skb, _abort_code);
+ ret = rxrpc_verify_response(conn, skb, _abort_code);
if (ret < 0)
return ret;
rxrpc-input-Open-code-skb_unshare.patch
--- a/net/rxrpc/input.c 2026-05-21 00:43:33.000000000 +0200
+++ b/net/rxrpc/input.c 2026-05-21 00:52:09.218999172 +0200
@@ -1286,19 +1286,20 @@
/* Unshare the packet so that it can be modified for in-place
* decryption.
*/
- if (sp->hdr.securityIndex != 0) {
- struct sk_buff *nskb = skb_unshare(skb, GFP_ATOMIC);
+ if (sp->hdr.securityIndex != 0 &&
+ skb_cloned(skb)) {
+ struct sk_buff *nskb = skb_copy(skb, GFP_ATOMIC);
if (!nskb) {
+ kfree_skb(skb);
rxrpc_eaten_skb(skb, rxrpc_skb_unshared_nomem);
goto out;
}
- if (nskb != skb) {
- rxrpc_eaten_skb(skb, rxrpc_skb_received);
- skb = nskb;
- rxrpc_new_skb(skb, rxrpc_skb_unshared);
- sp = rxrpc_skb(skb);
- }
+ consume_skb(skb);
+ rxrpc_eaten_skb(skb, rxrpc_skb_received);
+ skb = nskb;
+ rxrpc_new_skb(skb, rxrpc_skb_unshared);
+ sp = rxrpc_skb(skb);
}
break;
Especially this:
| *
| * Restart config...
| *
| *
| * Mitigations for CPU vulnerabilities
| *
| Mitigations for CPU vulnerabilities (CPU_MITIGATIONS) [Y/n/?] (NEW)
I do not know how you got the kernel compiled: It is impossible to compile the new release current with our configuration-files. So you either have done this via makepkg, which is the most dirty way to do. Or you have answered your own through the above questions, which is not acceptable as we do the full build-process with automatization.
Please refer to our guide for package-building here: https://wiki.hyperbola.info/doku.php?id … nvironment
We do not use makepkg alone to build packages, provide working patches (please control that in the process) and also have a full build-automation otherwise the package itself is seen as damaged until resolved.
Human being in favor with clear principles and so also for freedom in soft- and hardware!
Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!