From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1E46C433EF for ; Thu, 23 Dec 2021 10:19:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229713AbhLWKT2 (ORCPT ); Thu, 23 Dec 2021 05:19:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46364 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347657AbhLWKT0 (ORCPT ); Thu, 23 Dec 2021 05:19:26 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C974C061757; Thu, 23 Dec 2021 02:19:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: MIME-Version:References:In-Reply-To:Message-Id:Date:Subject:Cc:To:From:Sender :Reply-To:Content-Type:Content-ID:Content-Description; bh=c3sVg+FOnnrAjIuYNGgmpnKM7+jMk1UCUDYyQOig0Cg=; b=4VEs6C/AWs9iNVIRojm4c4Wsga Fxw4LE4BXsZ0E2wRV2IX51bRMFvpfO4QJ16rVJZcV26WyNY6VoUKucgbtfkdOB8UoUovNzlWqRVGN G3xRTg6kGZKPDvb55rM9aVUvhCC/8mzYHF0UFgf4069+uyQJyN/uSMoldVJ8uCv+BFZO1r0z2tBng h73phb20BSnvOUanZRf961rwDuFztEwyWJTZ6lWCBa1VgdWd2qXjdcVrZ7zjGXXP+m8J8q1p9+sPl 0RKIKX/xWx9i8nGnBBvJdamI9RXWzxu1UzZ0uznAnIH4csfDtksqJ9VMeeot2lmxqrzT3zeIqg9Dv u5xWnX7A==; Received: from [46.183.103.8] (helo=localhost) by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1n0LBs-00CTl9-DS; Thu, 23 Dec 2021 10:19:17 +0000 From: Christoph Hellwig To: Jonathan Corbet , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko Cc: Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , linux-doc@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org Subject: [PATCH 1/4] bpf, docs: Fix verifier references Date: Thu, 23 Dec 2021 11:19:03 +0100 Message-Id: <20211223101906.977624-2-hch@lst.de> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20211223101906.977624-1-hch@lst.de> References: <20211223101906.977624-1-hch@lst.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Use normal RST file reference instead of linkage copied from the old filter.rst document that does not actually work when using HTML output. Signed-off-by: Christoph Hellwig --- Documentation/bpf/instruction-set.rst | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Documentation/bpf/instruction-set.rst b/Documentation/bpf/instruction-set.rst index fa7cba59031e5..fa469078301be 100644 --- a/Documentation/bpf/instruction-set.rst +++ b/Documentation/bpf/instruction-set.rst @@ -203,7 +203,7 @@ Some core changes of the eBPF format from classic BPF: bpf_exit After the call the registers R1-R5 contain junk values and cannot be read. - An in-kernel `eBPF verifier`_ is used to validate eBPF programs. + An in-kernel verifier.rst is used to validate eBPF programs. Also in the new design, eBPF is limited to 4096 insns, which means that any program will terminate quickly and will only call a fixed number of kernel @@ -234,7 +234,7 @@ optimizations, socket filters and seccomp are using it as assembler. Tracing filters may use it as assembler to generate code from kernel. In kernel usage may not be bounded by security considerations, since generated eBPF code may be optimizing internal code path and not being exposed to the user space. -Safety of eBPF can come from the `eBPF verifier`_. In such use cases as +Safety of eBPF can come from the verifier.rst. In such use cases as described, it may be used as safe instruction set. Just like the original BPF, eBPF runs within a controlled environment, @@ -462,6 +462,3 @@ of two consecutive ``struct bpf_insn`` 8-byte blocks and interpreted as single instruction that loads 64-bit immediate value into a dst_reg. Classic BPF has similar instruction: ``BPF_LD | BPF_W | BPF_IMM`` which loads 32-bit immediate value into a register. - -.. Links: -.. _eBPF verifier: verifiers.rst -- 2.30.2