summaryrefslogtreecommitdiff
path: root/databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls
diff options
context:
space:
mode:
authorPalle Girgensohn <girgen@FreeBSD.org>2024-05-09 22:13:22 +0200
committerPalle Girgensohn <girgen@FreeBSD.org>2024-05-10 00:34:46 +0200
commitade1c57e3a72ec9c4a7c02ce28dbfbd5efcce373 (patch)
tree5a1be2c384a6472f3471f0e27acd58b1552f9465 /databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls
parentsecurity/vuxml: Document vulnerability in postgresql. (diff)
databases/postgresql??-*: Update to latest versions
PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19 Released! The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.3, 15.7, 14.12, 13.15, and 12.19. This release fixes one security vulnerability and over 55 bugs reported over the last several months. Please note that the fix in this release for CVE-2024-4317 only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after this fix is applied. If you have a current PostgreSQL installation and are concerned about this issue, please follow the additional updating instructions provided in the CVE-2024-4317 description or the release notes for the remediation. [1] The script is installed as /usr/local/share/postgresql/fix-CVE-2024-4317.sql PostgreSQL 12 will stop receiving fixes on November 14, 2024. If you are running PostgreSQL 12 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information. [1]: https://www.postgresql.org/support/security/CVE-2024-4317/ Security: d53c30c1-0d7b-11ef-ba02-6cc21735f730 PR: 277428 (remove unneded patch) PR: 260494 (remove deprecated INTDATE option) PR: 265860 (correct path for contrib README file in pkg-message)
Diffstat (limited to 'databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls')
-rw-r--r--databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls24
1 files changed, 0 insertions, 24 deletions
diff --git a/databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls b/databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls
deleted file mode 100644
index 02686061ce99..000000000000
--- a/databases/postgresql15-server/files/patch-disable-llvm-jit-inlining-with-tls
+++ /dev/null
@@ -1,24 +0,0 @@
-Do not inline functions which access TLS in LLVM JIT, as
-this leads to crashes with unsupported relocation error
-
-diff --git src/backend/jit/llvm/llvmjit_inline.cpp src/backend/jit/llvm/llvmjit_inline.cpp
-index 2617a46..a063edb 100644
---- src/backend/jit/llvm/llvmjit_inline.cpp
-+++ src/backend/jit/llvm/llvmjit_inline.cpp
-@@ -608,6 +608,16 @@ function_inlinable(llvm::Function &F,
- if (rv->materialize())
- elog(FATAL, "failed to materialize metadata");
-
-+ /*
-+ * Don't inline functions with thread-local variables until
-+ * related crashes are investigated (see BUG #16696)
-+ */
-+ if (rv->isThreadLocal()) {
-+ ilog(DEBUG1, "cannot inline %s due to thread-local variable %s",
-+ F.getName().data(), rv->getName().data());
-+ return false;
-+ }
-+
- /*
- * Never want to inline externally visible vars, cheap enough to
- * reference.