From nobody Tue Nov 01 22:20:56 2022 X-Original-To: freebsd-announce@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N24Gw51mYz4gBf2 for ; Tue, 1 Nov 2022 22:20:56 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N24Gw3LBmz3Vxb; Tue, 1 Nov 2022 22:20:56 +0000 (UTC) (envelope-from security-advisories@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1667341256; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=8CODW9CEecnEAJzH5x48vL7KJ8MK3ZTLLtDfmwWIPKY=; b=KxEHkdGlLVcIKlvV9J22nJ2R8yrO5NNUQRh7b80csurrOM0HvP+bVxH5rrHW67sv+uiLGM QtjPskVNBFO69o6agSFQnRG1FZ+T2oj6oWSzKcd8POduTP5jwUSD97wkS4rKN5LxVqrDWc r3uapZ0cEnsdubftdQ6lE1Dkk3miAKZOe5eZzxjvc10RJIDnh0cXLrGGtuzAZxIz28trzp K7tYkkkAdPpq2hVC9zqC0m3n/s4rXSUYq/aZS/Z1x7Q8Q4CAq7FdRoHCcrSsdEs5YP7/74 zHB8gbXA8RAw8La+zJmj6IkKX7tgI9NO6iEU51nyUqcFaLPoSC+n77NVgKtRiA== Received: by freefall.freebsd.org (Postfix, from userid 945) id 5B3923A05; Tue, 1 Nov 2022 22:20:56 +0000 (UTC) From: FreeBSD Errata Notices To: FreeBSD Errata Notices Subject: FreeBSD Errata Notice FreeBSD-EN-22:23.vm Reply-To: freebsd-stable@freebsd.org Precedence: bulk Message-Id: <20221101222056.5B3923A05@freefall.freebsd.org> Date: Tue, 1 Nov 2022 22:20:56 +0000 (UTC) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1667341256; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=8CODW9CEecnEAJzH5x48vL7KJ8MK3ZTLLtDfmwWIPKY=; b=UjLsMWzTnps0RPyAsK5Cvq4xThrQjEPbdvj4LIBU066yOuSdT/LzX5azWDYyXaTSrrDqki AmLEhXJnZsfEC1mJTOfeyEWNHOvzmPuLwv3ouulIVpjTar4yK0qoNDkKXQjd+L3nQQdBOt 3tvHgTzTzhm5L1DmkFIp+VoCAPyT69eUJLcm1Eg/WWzHz5crGSk6ERB0/ocdo22nz8rKA2 aHHLNdvoKJYcTdFmRUP7S85OJiKJJSHQqUdQe7+NRUC6yHWMxc7orYQPvq/0uW5Bj0o5FN OsJ+P1yqQ+xNkJgBSOVNWWMV04HQS9k8grcLAtXyehYfCKvxF1le1OZbUQ3C9g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1667341256; a=rsa-sha256; cv=none; b=Qle43uxNj0JmxNCeZsM+pD7VNyTRUhPz8I8Vm46M4kEifd7J4cyFEYPm6B5rJQVNtulZb3 ao8JxNsxHJ/X6lO4whQO4WCFBfP+IUyuq5ophsUB7+cWzDc9+VFZZnwNQ4HkZcpCf0HymT xrmAOn6CdalE//BRdRFu9hhLWw1aEC+jEuIMtfKHzq+LLlrwZf2y8uRALwTCKCJ8CQ70MG g2iAK38gU4DN5xSd6iElryme79b8bHItSWegwUVQk7/zbDsxDfo/d1CBiNuFF5fHmeALhD UJmAs5dZElhp8iPx63XKrhhfO84bedH2VXDjppY20XiyC8iF5xttQabPWMUx+A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N List-Id: Project Announcements [moderated] List-Archive: https://lists.freebsd.org/archives/freebsd-announce List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-announce@freebsd.org X-BeenThere: freebsd-announce@freebsd.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-EN-22:23.vm Errata Notice The FreeBSD Project Topic: Memory pages become unreclaimable Category: core Module: vm Announced: 2022-11-01 Affects: FreeBSD 13.1 Corrected: 2022-10-12 13:49:25 UTC (stable/13, 13.1-STABLE) 2022-11-01 13:28:11 UTC (releng/13.1, 13.1-RELEASE-p3) For general information regarding FreeBSD Errata Notices and Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The FreeBSD kernel's VM subsystem manages system memory. Among other responsibilities, it provides a page allocator and maintains a pool of free pages. When this pool is depleted, the VM reclaims allocated pages from a set of page queues. II. Problem Description In certain workloads, allocated pages are not enqueued as they should be, causing them to become unreclaimable when free memory is scarce. In some situations the memory may become available again following restarts of services (e.g., database servers) which are triggering the bug. III. Impact System memory could become inaccessible to the page daemon, resulting in less memory available for caching. In some cases this can result in out-of-memory process kills. IV. Workaround No workaround is available. V. Solution Upgrade your system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date and reboot. Perform one of the following: 1) To update your system via a binary patch: Systems running a RELEASE version of FreeBSD on the amd64, i386, or (on FreeBSD 13 and later) arm64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +5min "Installing errata update" 2) To update your system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/EN-22:23/vm.patch # fetch https://security.FreeBSD.org/patches/EN-22:23/vm.patch.asc # gpg --verify vm.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details This issue is corrected by the corresponding Git commit hash or Subversion revision number in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/13/ 6094749a1a5d stable/13-n252707 releng/13.1/ 4867d7d34dfd releng/13.1-n250160 - ------------------------------------------------------------------------- Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAmNhlqQACgkQ05eS9J6n 5cKKfg//f+YhLk47E5Bk/KZ07ONQ7xN0W9YZyz1P4iLc85LIaszC8+L8auwM+uR4 ufvo4ToDzbDq0v+2mHUdgQ7CVylOzAb114z8ZFADHhlBJeft5pdzm+/R3wfqADbm VL2I6uqjsQiH41umNgZQtyQh15LBWUlvrDd7r5dGVMzU0+VXNTngP58Jn7kqiUPg jwUQk6l/PPRLRGqX5RJHoz8traCLsd7i+58/FPyaofrtrwl97uxtcbBEcPvcXsrL yTnTcyPHnR8lqgmNXExcOPxfMBFz0sXgfDIXebnEP+inMx4gF2U3CBJuTCww8NWV M4R7bj1HjWw8WZV1dZUFB73qx4r51iKanYQsqFVEWl7KnhQL6zG8nCt4iPR0wiKJ x7qIRGtXCgzZieg0fQnsNjSdjjiIQmLCOq6BTmG1X5tcLF7hAM8D42RFGSbvLhNU cGP/1Gd1iK72VqBRCSHKhZi79//YA8lI+f3b7ORMB9Q5cmy9l0A0nMO2EpBdc7x/ 0VGSXMaVaegaKGb3vXteVvmqtHAWg2NiBMgUHb3oMEXdbjsymmgkCsTciuiYDLxQ Y/XdbtMHZi7VpZNS3Qt6wIpAEhSDxYsgf2+7/22Ni09Awn5H2/F3DCeo0dU8hWR1 gksYdLbwRI+By8hguqALkpC1lP/M8Hc/HBrEiG6OqY+OvZr43OA= =n7Mz -----END PGP SIGNATURE-----