Opened 2 years ago
Closed 2 years ago
#17457 closed enhancement (fixed)
mesa-22.3.2
Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
---|---|---|---|
Priority: | normal | Milestone: | 11.3 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New point version.
Change History (5)
comment:1 by , 2 years ago
follow-up: 3 comment:2 by , 2 years ago
2022-12-28 - Version 3.40.1
Version 3.40.1 is a patch release that fixes some obscure problems in version 3.40.0. The problems fixed have no impact on most applications. Upgrading is only necessary if you encounter problems.
The two most important fixes are these:
Fix the --safe command-line option on the CLI so that it correctly disallows functions with side-effects. This is a bug in the CLI — not a bug in the SQLite library — and it only affects the --safe command-line option, making that option less than fully "safe". As the number of systems that use the --safe command-line option in the CLI is approximately zero, this is not considered an important bug. However, a third-party wrote a CVE against it which caused considerable angst among maintainers, so it seems good to get the fix into circulation sooner rather than wait on the next major release.
The optional memsys5 memory allocator picked up a bug that might put it into an infinite loop for very large (500MiB) allocations. Almost all systems use their native memory allocator, not memsys5. Memsys5 is only used if SQLite is compiled using SQLITE_ENABLE_MEMSYS5 and then initialized using sqlite3_config(SQLITE_CONFIG_HEAP). Very, very few systems do this, and so the problem is not considered to be serious.
comment:3 by , 2 years ago
Replying to Bruce Dubbs:
2022-12-28 - Version 3.40.1
Version 3.40.1 is a patch release that fixes some obscure problems in version 3.40.0. The problems fixed have no impact on most applications. Upgrading is only necessary if you encounter problems.
The two most important fixes are these:
Fix the --safe command-line option on the CLI so that it correctly disallows functions with side-effects. This is a bug in the CLI — not a bug in the SQLite library — and it only affects the --safe command-line option, making that option less than fully "safe". As the number of systems that use the --safe command-line option in the CLI is approximately zero, this is not considered an important bug. However, a third-party wrote a CVE against it which caused considerable angst among maintainers, so it seems good to get the fix into circulation sooner rather than wait on the next major release.
The optional memsys5 memory allocator picked up a bug that might put it into an infinite loop for very large (500MiB) allocations. Almost all systems use their native memory allocator, not memsys5. Memsys5 is only used if SQLite is compiled using SQLITE_ENABLE_MEMSYS5 and then initialized using sqlite3_config(SQLITE_CONFIG_HEAP). Very, very few systems do this, and so the problem is not considered to be serious.
I suspect this pertains to #17456 (sqlite)...
comment:4 by , 2 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 2 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed at commits
0d1c01ea02 Update to opencv-4.7.0. 8e874375c0 Update to sqlite-autoconf-3400100. 959291ff80 Update to mesa-22.3.2.
Release notes are at https://docs.mesa3d.org/relnotes/22.3.2.html