From: Yauheni Kaliuta <ykaliuta@redhat.com>
To: Johan Almbladh <johan.almbladh@anyfinetworks.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: test_kmod.sh fails with constant blinding
Date: Thu, 01 Sep 2022 13:01:31 +0300 [thread overview]
Message-ID: <xuny7d2ne7lw.fsf@redhat.com> (raw)
In-Reply-To: <CANoWswnQK4NfvmNjN9DZpeq5ry4qXra9m1hSrBexT83CzUuR0w@mail.gmail.com> (Yauheni Kaliuta's message of "Tue, 5 Jul 2022 11:31:58 +0300")
Hi, Johan!
>>>>> On Tue, 5 Jul 2022 11:31:58 +0300, Yauheni Kaliuta wrote:
> Hi, Johan!
> On Tue, Jul 5, 2022 at 11:06 AM Johan Almbladh
> <johan.almbladh@anyfinetworks.com> wrote:
>>
>> On Mon, Jul 4, 2022 at 10:22 AM Yauheni Kaliuta <ykaliuta@redhat.com> wrote:
>> >
>> > Hi!
>> >
>> > On Fri, Jul 1, 2022 at 2:05 PM Yauheni Kaliuta <ykaliuta@redhat.com> wrote:
>> > > >>>>> On Thu, 30 Jun 2022 22:57:37 +0200, Daniel Borkmann wrote:
>> > >
>> > > > On 6/30/22 3:19 PM, Yauheni Kaliuta wrote:
>> > > >> Hi!
>> > > >> test_kmod.sh fails for hardened 2 check with
>> > > >> test_bpf: #964 Staggered jumps: JMP_JA FAIL to select_runtime
>> > > >> err=-524
>> > > >> (-ERANGE during constant blinding)
>> > > >> Did I miss something?
>> > >
>> > > > That could be expected if one of bpf_adj_delta_to_imm() / bpf_adj_delta_to_off()
>> > > > fails given the targets go out of range.
>> > >
>> > > I believe that, but how to fix the test? It should not fail.
>> > >
>> > > > How do the generated insn look?
>> > >
>> > > The instruction when it fails is
>> > >
>> > > (gdb) p/x insn[0]
>> > > $8 = {code = 0xb7, dst_reg = 0x0, src_reg = 0x0, off = 0x0, imm = 0x2aaa}
>> > >
>> > > And it's rewritten as
>> > >
>> > > (gdb) p rewritten
>> > > $9 = 3
>> > > (gdb) p/x insn_buff[0]
>> > > $10 = {code = 0xb7, dst_reg = 0xb, src_reg = 0x0, off = 0x0, imm = 0x68ad0283}
>> > > (gdb) p/x insn_buff[1]
>> > > $11 = {code = 0xa7, dst_reg = 0xb, src_reg = 0x0, off = 0x0, imm = 0x68ad2829}
>> > > (gdb) p/x insn_buff[2]
>> > > $12 = {code = 0xbf, dst_reg = 0x0, src_reg = 0xb, off = 0x0, imm = 0x0}
>> > >
>> > > IIUC.
>> > >
>> >
>> > Johan, what do you think?
>>
>> Hmm, I can take a look at it. What is the target arch?
>>
> It fails even on x86.
Did you have a chance to look?
--
WBR,
Yauheni Kaliuta
next prev parent reply other threads:[~2022-09-01 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 13:19 test_kmod.sh fails with constant blinding Yauheni Kaliuta
2022-06-30 20:57 ` Daniel Borkmann
2022-07-01 11:05 ` Yauheni Kaliuta
2022-07-04 8:21 ` Yauheni Kaliuta
2022-07-05 8:07 ` Johan Almbladh
2022-07-05 8:31 ` Yauheni Kaliuta
2022-09-01 10:01 ` Yauheni Kaliuta [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 15:11 Bram Schuur
2024-01-02 16:56 ` Yonghong Song
2024-01-02 17:47 ` Eduard Zingerman
2024-01-02 19:41 ` Yonghong Song
2024-01-02 22:39 ` Eduard Zingerman
2024-01-03 0:02 ` Jan-Gerd Tenberge
2024-01-03 7:23 ` Bram Schuur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xuny7d2ne7lw.fsf@redhat.com \
--to=ykaliuta@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=johan.almbladh@anyfinetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox