From nobody Thu Apr 9 14:09:02 2026 Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) (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 B521126290 for ; Sun, 8 Mar 2026 03:19:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.219.53 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772939948; cv=none; b=lJdOFd4c7aNRKZbHbOHOEWlpStMd6B1YDLH7r+6MKTOEIFfvHX+WhsuiAdZ3hZrTRPj28zSB9xNoGEsAAcgTFQaGa/ZCVG/G54V27YY4TLV/KmeycKG+mvQcuYR2Fv+RcZH7pRIOtNk4VRThk+ma4B2LOH476lxA5SskSi5BwHk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772939948; c=relaxed/simple; bh=dy/k8Ld8lreAZZpwnSwCEzMD/M4mnZXel/sJ/te+YEc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ubZKjs++H9n2+xWzf7P816BKDAe2WrxhaOTwfYsmnwH5pJXX9agYjVBnDsHCLOftV8nLotrNk1ROtDrrEsow4urach8dNIG+d0X1hdbbzZxTQuSgO11zeE/dO+qERUGjFi8eKIvU+0Tm7dKCoLD5fSP3xOo+CC3/KpIlwCTGokQ= 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=GVNlos+5; arc=none smtp.client-ip=209.85.219.53 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="GVNlos+5" Received: by mail-qv1-f53.google.com with SMTP id 6a1803df08f44-89a000f5adeso125405016d6.3 for ; Sat, 07 Mar 2026 19:19:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1772939945; x=1773544745; 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=/5PPTP1bytZy0bNsMCBbdG+U9hPc2DiZHiMu5MgnVGQ=; b=GVNlos+5TSYZQRR8TNnt+Q3TmNtfjaw2icEcv5T6aQOcNq/GD4aR/i6ZYvkgsQFHln PbvykDXNovS6KMGt6pfzRjYJu67MmVR7MLcWM4dW6fb3Qn68AqcaxJItdXr28k0EZ69w EqvlgsCh02mqaiA36iSqiIPxxmnqvxb8VzDm19zw0w+Qfhh6SGm9XhEPZWDRfy+EWGpL xdG3JZ4cemxOod04rPEj3VoED+vGzAsbZz10Wl2oO+drTkDiird9AZN8XvtQQuqQRzsW 0lQaXh8x+7OrFhcI9SN6ncWsCn3aIWasuV2rGNBCWTeHGMIrIJMY3F/KbqzzEsTsyJOF EZxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772939945; x=1773544745; 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=/5PPTP1bytZy0bNsMCBbdG+U9hPc2DiZHiMu5MgnVGQ=; b=tHWKQkcqMD5/oGRYxbl8yT/qNwjW4MpDJuVayp4luWR/6PDzKrSqWtg8uGS515ZWKp 2pyRJs+o2cslBVs9YgNE9bmfVXuhBATrHsQWHSxZu+EdgFabQrRrhqS4+Y9t+lQ165X5 YRkovJBYyKlc3AffDJq67Pw9OYELjl/GYKSN7ddOB4Q0efry+xzO0IN3JDnemi5Kp+66 HTz2rudS6wikhpFYi+TqoPWeqnNOhU2mZx0GQPA+/5h5wVNH+QjYL/YNsEOOs1pob5hz KcyyW8nCgl///0DXT61j6TZI/LDHMbBKG2TZJXxSblw9RraWfxVVdgmzO2Y+BYN8Q5kU JSdA== X-Forwarded-Encrypted: i=1; AJvYcCW1peS61fio0ZXoDfmFkK0ZlK/OU2mr/a+eUCwXqeRFsSqCTutyaSZJopWovGgFQc0v7zlb5WzqBiMXg2Q=@vger.kernel.org X-Gm-Message-State: AOJu0YzrBQm65DAaO2VDwD9s+B8ZrokYo5skbaBPYc+1ipaTTcgQghIT g7GmmeA6yZJfAdn0YWm/m6rFO6MVvdX8UiVatJ1n+hUocN7E8VX+CmG/ X-Gm-Gg: ATEYQzzEZce71APT6P0xO36txMnyW4aEhJMi7xNwC8HTo/reDMonwRPEuTt5+HSBYhY 1pWZPvcyByi9K4z/7TJPjjKfBj+XxCHkcbTIi4gUl0EKRn2Mal2b0KxAruxo2A/mq1g/uWlkrWU PfBxInLvRYjtSXFBFeSyBO43oCMSUC58G5IZry58KUt0wi3v02QV7fHKGwIXZS8sB27dI/1/d4V FPBpX10iNTQ4FTEVG2bg0s50HMW18f3Zo+k9zOE5lkjP/F/X4TaQkoe+QUvI+stoXS4xQiYyWWI j6dGwVvdmN/tZiyiK7gOeKzKn+DBKhd85ZRVs04oL0Neynh6SR3lsIIrxoEkvs1G4Fo8XZGPZAy 49lBFi4IYXUF/59oJRu7E4y1W8cjNAEfYYNVTV6dPgl9JkjyYQzVYVZ36rUX3iPiT9VUH4NIVSi ODwwO02/5XiFlKHwjTF2YQECH1Ji7lXqZw02+AShV2dqWVX2JrrXOSqVYjUHI4FqlCW9ZpZweNv Bgj X-Received: by 2002:a05:622a:1914:b0:4f1:e9da:e876 with SMTP id d75a77b69052e-508f499ef56mr92284771cf.62.1772939944685; Sat, 07 Mar 2026 19:19:04 -0800 (PST) Received: from Ecomp.localdomain ([163.252.225.68]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-508fd453ff3sm31481581cf.17.2026.03.07.19.19.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 07 Mar 2026 19:19:04 -0800 (PST) From: Evan Ducas To: wufan@kernel.org, corbet@lwn.net, skhan@linuxfoundation.org Cc: linux-security-module@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Evan Ducas Subject: [PATCH] docs: security: ipe: fix typos and grammar Date: Sat, 7 Mar 2026 22:16:33 -0500 Message-ID: <20260308031633.28890-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 --- Documentation/security/ipe.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/security/ipe.rst b/Documentation/security/ipe.rst index 4a7d953abcdc..d29824d7fd2d 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,7 +235,7 @@ 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 +trusted applications, keys roll, etcetera). Updating a kernel to change 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 @@ -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