| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <028617ef5663bf2f9901701630d223fed88e519d2020e3317bfffb4ef5cb123b@mail.kernel.org> Date: Tue, 10 Feb 2026 14:12:07 +0000 (UTC) From: bot+bpf-ci@...nel.org To: jolsa@...nel.org,andrii@...nel.org Cc: bpf@...r.kernel.org,linux-kernel@...r.kernel.org,songliubraving@...com,yhs@...com,john.fastabend@...il.com,ast@...nel.org,andrii@...nel.org,daniel@...earbox.net,martin.lau@...nel.org,eddyz87@...il.com,yonghong.song@...ux.dev,clm@...a.com,ihor.solodrai@...ux.dev Subject: Re: [PATCHv2 bpf-next 3/5] selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch > selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch This isn't a bug, but there's a typo in the subject line. "no5" should be "nop5". > Now that we have no5 optimization support in kernel, let's emit The same typo appears here in the commit body. --- AI reviewed your patch. Please fix the bug or email reply why it's not a bug. See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md CI run summary: https://github.com/kernel-patches/bpf/actions/runs/21867569087 AI-authorship-score: low AI-authorship-explanation: The commit shows typical human development patterns including a typo in the commit message, iterative design changes between v1 and v2 based on real-world testing, and normal kernel mailing list review interactions. issues-found: 1 issue-severity-score: low issue-severity-explanation: Single typo in commit message subject and body where 'no5' should be 'nop5'; does not affect code functionality.
Powered by blists - more mailing lists