openldap-bugs

openldap-bugs@openldap.org

1 participants
20895 discussions

[Issue 8010] LMDB: New mdb_txn_begin() flag to init as reset
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=8010 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Howard Chu <hyc(a)openldap.org> --- *** This issue has been marked as a duplicate of issue 8250 *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8250] Allowing transaction to be created in the reset state
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=8250 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott(a)gameranger.com --- Comment #4 from Howard Chu <hyc(a)openldap.org> --- *** Issue 8010 has been marked as a duplicate of this issue. *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8124] Patch "Context for compare functions"
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=8124 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Howard Chu <hyc(a)openldap.org> --- *** This issue has been marked as a duplicate of issue 7980 *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7980] LMDB added support for user context in compare function
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7980 --- Comment #2 from Howard Chu <hyc(a)openldap.org> --- *** Issue 8124 has been marked as a duplicate of this issue. *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7980] LMDB added support for user context in compare function
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7980 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Howard Chu <hyc(a)openldap.org> --- Not needed. Pass additional state using the MDB_val *a pointer. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7853] Improve safety of mdb_env_close
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7853 --- Comment #4 from Howard Chu <hyc(a)openldap.org> --- (In reply to dw(a)hmmz.org from comment #0) > Full_Name: David Wilson > Version: LMDB 0.9.11 > OS: > URL: > https://raw.githubusercontent.com/dw/py-lmdb/master/misc/readers_mrb_env. > patch > Submission from: (NULL) (178.238.153.20) > > > Currently if a user (wilfully or accidentally, say, through composition of > third party libs) opens the same LMDB environment twice within a process, and > maintains active read transactions at the time one mdb_env_close() is called, > all reader slots will be deallocated in all environments due to the logic > around line 4253 that unconditionally clears reader slots based on PID. > > I'd like to avoid this in py-lmdb, and seems there are a few alternatives to > fix it: > 4) Modify lock.mdb to include MDB_env* address within the process, and update > mdb_env_close() to invalidate only readers associated with the environment > being closed. I dislike using the MDB_env* as an opaque publicly visible > cookie, but perhaps storing this field might be reused for other things in > future. I was looking at this approach, which initially seems harmless. But unfortunately it does nothing to address the fact the fcntl lock on the lock file will still go away on the first env_close() call. If there are no other processes with the env open, then the next process that opens the env will re-init the lock file, because it doesn't know about the existing process. At that point the existing process is hosed anyway. So the question is, if a process has made the mistake of opening the same env twice, what is the anticipated lifetime of each env instance? If the code was written according to doc guidelines, then both env instances should only be closed after all processing is done and just before program exit. In that case it doesn't really matter what happens to the reader table or the fcntl lock. But if the two instances have drastically different lifetimes, then all bets are off. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7842] mdb readers/writer exclusion protocol, as implemented, is racy.
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7842 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Howard Chu <hyc(a)openldap.org> --- *** This issue has been marked as a duplicate of issue 7969 *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7969] LMDB: Globally shared fields of meta-data are not 'volatile'.
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7969 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsbx(a)acm.org --- Comment #18 from Howard Chu <hyc(a)openldap.org> --- *** Issue 7842 has been marked as a duplicate of this issue. *** -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7969] LMDB: Globally shared fields of meta-data are not 'volatile'.
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7969 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #17 from Howard Chu <hyc(a)openldap.org> --- Patch committed, fix released in LMDB 0.9.15 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7668] LMDB enhancement, corruption detection
by openldap-its＠openldap.org 02 Jun '21

02 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7668 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |TEST --- Comment #2 from Howard Chu <hyc(a)openldap.org> --- MDB_PREVSNAPSHOT flag was added for LMDB 1.0 to allow opening env with the previous instead of current meta page. mdb_env_set_checksum() was added for LMDB 1.0 to allow specifying per-page checksums. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs