From nobody Thu Apr 9 13:26:17 2026 Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D88E636212D for ; Sun, 8 Mar 2026 18:09:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.219.47 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772993398; cv=none; b=PQZSRygafcMMB5AkFXHzQ36z6m8YrNEbML/GLU3ApyLIYs8CMDzvqhnuTR8V3itLLammxz91fN5q+Va+GYo/u03fkIwVngVhuI5LNS3Ib6Zb4CoB4RHVYAf31sfpobCkho8lcvoE/vmMfo6l9L79n7Apn3+wIVbQvmgE/04AKjs= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772993398; c=relaxed/simple; bh=XmsYEmCoXNT/C2GWn7qZw2zbifEAERePDgg8h4oumeg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=sSd8MvfYSbWbC8QZzjZ+M8zjvp8SWDPqBJ3IgaEBP7nICVqtXK1Zpa1yc7bnsE+PrB7XLhvHb5WYdSE7UvHG5GMRfZRHxDKUjbidFzyeruGtH+AutTceSkdm4hFzbcpQqpZ5xackPzgc+uxvkSeDqtFzYHz+g/8eVik4bWN18GE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=dtDHfvUJ; arc=none smtp.client-ip=209.85.219.47 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="dtDHfvUJ" Received: by mail-qv1-f47.google.com with SMTP id 6a1803df08f44-89a0ece9f14so83497996d6.3 for ; Sun, 08 Mar 2026 11:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1772993396; x=1773598196; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=Iqw/4Eli0nG5osMBUIJSgBSBQi9kdXgUAruDyKaARRE=; b=dtDHfvUJ1WFF2sTZDvvFrFtg6D81PCInwoXsetZzb5DpU5b3C46gcNb79o5Bru/Q2e t82TkAz8NFOBBK8c4sWkeDrJhq/shnd6ZHBo5stpeKkGZ86evX39vddEBS4WyH3Erskk HW3yyKcL6vGKkd8tptIHDEFdMnF6QS6AEXs8XqbgHWgAIRkvgkvHOUzKRJxt9e8VzEBx LvwqFoA0NIsM9J1/VyEVYgsblRNp5ES6seqgiDcZ99Zalj+RSMVTVSjGB8mnJ7vWhGby S8lNiRDdpGqNLr0GEKLz9Wv8hgOi/6BNMfPkiJRt2jauNJJmnQW3BKcaPTujmSyaDQ5R oA9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772993396; x=1773598196; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Iqw/4Eli0nG5osMBUIJSgBSBQi9kdXgUAruDyKaARRE=; b=OX397PmgPOQPhqnnQXLAeA9TSHsSK4NRrkRPoTXdjOSev32WV47zPkq55++ES7rDR9 FjD3+IsFlp4+0z7oFXNsw+5IJGyt7hriuXr85qspZeMBPSeEqxBGvw+YV5SP3OxOnZn1 aP4bogFcQgeVa/KtmWFtYm1iHFaBekgEjE8J3Z6+mEB23brF1EYf6mPjVybQxAJCDn5+ CHEISHH4lLYTTtuU1mRCyWANba7rUZCFHtmVSmm2oMnjInz7+CDA9029w6dygBZCHebN pBUMJ3ifA31VHvgSsydSXWZgQCL+2AFEs6V+XzmzcII6uVIx3yxW63sBamazLCnYrUOe rxvw== X-Forwarded-Encrypted: i=1; AJvYcCUIBoIYE0PMEoMn1IDbzrA0ct+Cx3tpLLNsXB3CgQGcQap7B6sUEsJGi8QK9MDFzyzBuYf5QJu+CDC4syc=@vger.kernel.org X-Gm-Message-State: AOJu0YyP8hk74sMeXcakkJJRsIBiY9Wga0ybcNAiIh65WQ7eZuNd7hQR HvQXsnp/ge+uvlAl4zXwKe5nkdWwad75I/w9zhER5Se10IqubXsXBUtl X-Gm-Gg: ATEYQzxjBgnEcHAEKUXmdod57NFIty+/zZcWZGZtqiDYkf96NZenHHt6d2ITCOmDSZw fcdW94T74Rm/5qyfHvbSS0Xk0CFal4BdWbJU2EPzluURVYCYA0XzoO3dxdUL7Gcl7oZ3jQG8zHl NBwSQ8IOuSqSjbPRcqfgKOviG7+ezXABpBkkd3hccnsmGUmUlLinAhsRUu8WwUnM/IMZfeOBbUg /une9JLkq8WG7Cq102DzZhAnC5WX+xDBpuyD7r+Yc8GXEHKCSxNCpE6wxJ0/0mCBbe5U2y/S5I6 128YQE8gyQZXiqW7+KK/noK4qG2Lc+Kwf/Mir0+F6lrU0tD+qxcrWJMoAtj1g8x2tdpATJiO1wW 8KAB4Va944kcvk6nJMBLVRJbJrdQ8n0CZ1O/vxByZdTG/6R5GMEdSjJBk9Cw4Q1LunGUVqJJLvR 7PdV3KhF0l9IC7UoFueWxUAaguiBYxIWlAm+01j/Ms20wWO1ewg59Mzc0nW189p3iNqw== X-Received: by 2002:a05:6214:c2a:b0:89a:1536:2529 with SMTP id 6a1803df08f44-89a30a31b87mr120367666d6.15.1772993395869; Sun, 08 Mar 2026 11:09:55 -0700 (PDT) Received: from Ecomp.localdomain ([163.252.225.68]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-89a31719574sm63773696d6.48.2026.03.08.11.09.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Mar 2026 11:09:55 -0700 (PDT) From: Evan Ducas To: wufan@kernel.org, corbet@lwn.net, skhan@linuxfoundation.org Cc: rdunlap@infradead.org, bagasdotme@gmail.com, linux-security-module@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Evan Ducas Subject: [PATCH v2] docs: security: ipe: fix typos and grammar Date: Sun, 8 Mar 2026 14:07:34 -0400 Message-ID: <20260308180734.5792-1-evan.j.ducas@gmail.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Fix several spelling and grammar mistakes in the IPE documentation. No functional change. Signed-off-by: Evan Ducas Acked-by: Bagas Sanjaya Acked-by: Randy Dunlap --- Documentation/security/ipe.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/security/ipe.rst b/Documentation/security/ipe.rst index 4a7d953abcdc..5eb3e6265fbd 100644 --- a/Documentation/security/ipe.rst +++ b/Documentation/security/ipe.rst @@ -18,7 +18,7 @@ strong integrity guarantees over both the executable code= , and specific *data files* on the system, that were critical to its function. These specific data files would not be readable unless they passed integrity policy. A mandatory access control system would be present, and -as a result, xattrs would have to be protected. This lead to a selection +as a result, xattrs would have to be protected. This led to a selection of what would provide the integrity claims. At the time, there were two main mechanisms considered that could guarantee integrity for the system with these requirements: @@ -195,7 +195,7 @@ of the policy to apply the minute usermode starts. Gene= rally, that storage can be handled in one of three ways: =20 1. The policy file(s) live on disk and the kernel loads the policy prior - to an code path that would result in an enforcement decision. + to a code path that would result in an enforcement decision. 2. The policy file(s) are passed by the bootloader to the kernel, who parses the policy. 3. There is a policy file that is compiled into the kernel that is @@ -235,8 +235,8 @@ Updatable, Rebootless Policy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =20 As requirements change over time (vulnerabilities are found in previously -trusted applications, keys roll, etcetera). Updating a kernel to change the -meet those security goals is not always a suitable option, as updates are = not +trusted applications, keys roll, etcetera), updating a kernel to meet +those security goals is not always a suitable option, as updates are not always risk-free, and blocking a security update leaves systems vulnerable. This means IPE requires a policy that can be completely updated (allowing revocations of existing policy) from a source external to the kernel (allo= wing @@ -370,7 +370,7 @@ Simplified Policy: Finally, IPE's policy is designed for sysadmins, not kernel developers. In= stead of covering individual LSM hooks (or syscalls), IPE covers operations. Thi= s means instead of sysadmins needing to know that the syscalls ``mmap``, ``mprotec= t``, -``execve``, and ``uselib`` must have rules protecting them, they must simp= le know +``execve``, and ``uselib`` must have rules protecting them, they must simp= ly know that they want to restrict code execution. This limits the amount of bypas= ses that could occur due to a lack of knowledge of the underlying system; whereas t= he maintainers of IPE, being kernel developers can make the correct choice to= determine --=20 2.43.0