Update README #809
Closed
Update README #809
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
¬¬ |
Author
|
resume is here , it will be updated day by day |
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Apr 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but gives no indication of failures. This leads to cryptic log messages: (e.g. test_bpf) test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Pending a future fix, add a JIT warning to clarify the error: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load from literal pool: offset out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 3, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but gives no indication of failures. This leads to cryptic log messages: (e.g. test_bpf) test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Pending a future fix, add a JIT warning to clarify the error: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load from literal pool: offset out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 6, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 7, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 9, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 15, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 17, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 22, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 24, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
May 29, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 15, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 18, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 20, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 24, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 26, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jun 28, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 2, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 3, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 4, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 6, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 8, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 10, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 12, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 15, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 18, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Jul 19, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Sep 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Sep 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 1, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 10, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 11, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 15, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 20, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 21, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 21, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 21, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 27, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 28, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Oct 30, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 3, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 5, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 5, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 7, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 15, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 16, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 20, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 22, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 23, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 23, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 23, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 25, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
guidosarducci
added a commit
to guidosarducci/linux
that referenced
this pull request
Nov 26, 2025
On pre-ARMv7 archs, the JIT employs a literal pool for immediate loads but on failure returns a generic error code with no logging. This can lead to cryptic log messages (e.g. test_bpf): test_bpf: torvalds#809 ALU64_MOV_X: register combinations FAIL to select_runtime err=-524 test_bpf: torvalds#810 ALU64_AND_X: register combinations FAIL to select_runtime err=-524 Return a suitable error code and add a JIT warning to clarify the problem: test_bpf: torvalds#809 ALU64_MOV_X: register combinations load offset to literal pool out of range FAIL to select_runtime err=-524 Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.