From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Леонид Юрьев (Leonid Yuriev)" <leo@yuriev.ru>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libmdbx: bump version to 0.12.12
Date: Mon, 28 Oct 2024 16:41:18 +0100 [thread overview]
Message-ID: <20241028164118.1f770fb2@windsurf> (raw)
In-Reply-To: <20241027193029.298728-1-leo@yuriev.ru>
On Sun, 27 Oct 2024 22:30:28 +0300
Леонид Юрьев (Leonid Yuriev) <leo@yuriev.ru> wrote:
> This is bugfix release of stable libmdbx branch.
>
> The most significant fixes since v0.12.10 (the previous version pinned to
> buildroot):
>
> - Fixed the possibility of `SIGSEGV` inside the `coherence_check()` after
> changing the geometry by another process with an increase in the upper
> DB size above the previous in-process limit.
>
> - Fixed cursor(s) handling opened in parent transactions and closed before
> the completion of nested/child transactions. In such case, closed
> cursors were "resurrected", which led to a leak of memory allocated for
> such cursors.
>
> - Fixed a possibility of `SIGSEGV` when enabling logging of the
> `MDBX_LOG_TRACE` level in debug builds.
>
> - Correction of the missing `TXN_END_EOTDONE` in the case the start of
> a reading transaction fails. The mentioned bit-flag was missing in the
> transaction destruction/shutdown path on error its launch. Because of
> this, an attempt was made to destroy the cursors, which led to crash
> debug builds, since the corresponding array is intentionally filled
> with poison pointers.
>
> - Modification of `mdbx_close_by()` to return an error when trying to
> close the dbi descriptor of a table created and/or modified in a
> still-running transaction. Such premature closure of the descriptor is
> an incorrect use of the API and a violation of the contract/preconditions
> formulated in the description of `mdbx_close_dbi()`.
>
> However, instead of returning an error, an incorrect closure of the
> descriptor was performed, which could lead to the creation of a table
> with an empty name, leakage of database pages and/or corruption of a
> b-tree structure (wrong reference to the root of a table).
>
> The complete ChangeLog:
> https://gitflic.ru/project/erthink/libmdbx/blob?file=ChangeLog.md
>
> Signed-off-by: Леонид Юрьев (Leonid Yuriev) <leo@yuriev.ru>
> ---
> package/libmdbx/libmdbx.hash | 2 +-
> package/libmdbx/libmdbx.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-28 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 19:30 [Buildroot] [PATCH] package/libmdbx: bump version to 0.12.12 Леонид Юрьев (Leonid Yuriev)
2024-10-28 15:41 ` Thomas Petazzoni via buildroot [this message]
2024-11-13 8:18 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241028164118.1f770fb2@windsurf \
--to=buildroot@buildroot.org \
--cc=leo@yuriev.ru \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox