All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	bpf@vger.kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH bpf-next] bpf: Clear subreg_def for global function return values
Date: Fri, 12 Feb 2021 11:31:19 +0200	[thread overview]
Message-ID: <xunytuqhtyxk.fsf@redhat.com> (raw)
In-Reply-To: <20210212040408.90109-1-iii@linux.ibm.com> (Ilya Leoshkevich's message of "Fri, 12 Feb 2021 05:04:08 +0100")

Hi, Ilya!

>>>>> On Fri, 12 Feb 2021 05:04:08 +0100, Ilya Leoshkevich  wrote:

 > test_global_func4 fails on s390 as reported by Yauheni in [1].
 > The immediate problem is that the zext code includes the instruction,
 > whose result needs to be zero-extended, into the zero-extension
 > patchlet, and if this instruction happens to be a branch, then its
 > delta is not adjusted. As a result, the verifier rejects the program
 > later.

Thank you for addressing that!

 > However, according to [2], as far as the verifier's algorithm is
 > concerned and as specified by the insn_no_def() function, branching
 > insns do not define anything. This includes call insns, even though
 > one might argue that they define %r0.

I still think that the patching code should be fixed as well,
even if it's a separate issue.

But I got the attitude.

 > This means that the real problem is that zero extension kicks in at
 > all. This happens because clear_caller_saved_regs() sets BPF_REG_0's
 > subreg_def after global function calls. This can be fixed in many
 > ways; this patch mimics what helper function call handling already
 > does.

 > [1] https://lore.kernel.org/bpf/20200903140542.156624-1-yauheni.kaliuta@redhat.com/
 > [2]
 > https://lore.kernel.org/bpf/CAADnVQ+2RPKcftZw8d+B1UwB35cpBhpF5u3OocNh90D9pETPwg@mail.gmail.com/

 > Fixes: 51c39bb1d5d1 ("bpf: Introduce function-by-function verification")
 > Reported-by: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
 > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
 > ---
 >  kernel/bpf/verifier.c | 3 ++-
 >  1 file changed, 2 insertions(+), 1 deletion(-)

 > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
 > index beae700bb56e..183fae996ad0 100644
 > --- a/kernel/bpf/verifier.c
 > +++ b/kernel/bpf/verifier.c
 > @@ -5211,8 +5211,9 @@ static int check_func_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
 >  					subprog);
 >  			clear_caller_saved_regs(env, caller->regs);
 
 > -			/* All global functions return SCALAR_VALUE */
 > +			/* All global functions return a 64-bit SCALAR_VALUE */
 >  			mark_reg_unknown(env, caller->regs, BPF_REG_0);
 > +			caller->regs[BPF_REG_0].subreg_def = DEF_NOT_SUBREG;
 
 >  			/* continue with next insn after call */
 >  			return 0;
 > -- 

 > 2.29.2


-- 
WBR,
Yauheni Kaliuta


  reply	other threads:[~2021-02-12  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12  4:04 [PATCH bpf-next] bpf: Clear subreg_def for global function return values Ilya Leoshkevich
2021-02-12  9:31 ` Yauheni Kaliuta [this message]
2021-02-15 22:50 ` patchwork-bot+netdevbpf

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=xunytuqhtyxk.fsf@redhat.com \
    --to=yauheni.kaliuta@redhat.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=iii@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.