On 6/7/19 1:49 AM, quanah(a)symas.com wrote:
> --On Friday, January 25, 2019 9:25 PM +0000 michael(a)stroeder.com wrote:
>
>> All links herein are dead:
>> https://www.openldap.org/faq/data/cache/220.html
>>
>> I'd suggest to remove this FAQ page completely.
>
> I tried, but unfortunatley the FAQ software breaks Apache when you try and
> delete an answer. I think the better solution is just to remove the FAQ
> software completely.
The FAQ contains the only documentation for set-based ACLs.
So it's not an option to just shutdown FAQ-O-MATIC.
Ciao, Michael.
On Thu, Jun 6, 2019 at 7:39 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote:
>
> --On Thursday, March 07, 2019 10:10 AM +0000 noloader(a)gmail.com wrote:
>
> > Full_Name: JW
> > Version: 2.4.47
> > OS: Linux (Fedora 29, x86_64, fully patched)
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (151.196.22.177)
> >
> > I added -fsanitize=undefined to CFLAGS.
>
> In this case, the compiler is the problem.
I'm pretty sure the compiler is correct.
The instrumentation does not produce false positives. It operates on
real data and simply does not produce false positives.
> LMDB is 100% correct regarding
> alignment on all supported CPUs (which is most of them). The x86 family
> fully supports unaligned access, so LMDB makes use of this.
It is not the processor; it is the C language. The C language does not allow it.
> On other CPUs,
> which do not support unaligned access (e.g., SPARC), LMDB doesn't use them.
The undefined behavior exists even after disabling the unaligned
accesses with custom patches. For example, there is still undefined
behavior even after changes like this:
-#if defined(__i386) || defined(__x86_64)
-#define MISALIGNED_OK 1
-#else
#define ALIGNER (sizeof(size_t)-1)
-#endif
We also fixed COPY_PGNO but the undefined behavior remained.
The GCC Compile Farm (https://cfarm.tetaneutral.net/machines/list/)
has three SPARC machines. SPARC does not tolerate unaligned accesses
well, especially due to the optimized 64-bit move instruction.
OpenLDAP might consider testing on the SPARC machines.
In the bigger picture, OpenLDAP is causing other program and library
testing to fail testing. When we test other programs and libraries
that depend upon OpenLDAP in a similar fashion, the undefined behavior
in OpenLDAP surfaces in the other program and libraries. It is making
a lot of extra work for folks who perform extra testing.
I encourage OpenLDAP to fix the undefined behavior. OpenLDAP is an
important project, and the undefined behavior is causing too many
tangential problems.
Jeff
Hello,
There is no bug here. Your configuration is invalid. If you need help
with configuring OpenLDAP, then please use the
openldap-technical(a)openldap.org mailing list.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Friday, January 25, 2019 9:25 PM +0000 michael(a)stroeder.com wrote:
> All links herein are dead:
> https://www.openldap.org/faq/data/cache/220.html
>
> I'd suggest to remove this FAQ page completely.
I tried, but unfortunatley the FAQ software breaks Apache when you try and
delete an answer. I think the better solution is just to remove the FAQ
software completely.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Thursday, March 07, 2019 10:10 AM +0000 noloader(a)gmail.com wrote:
> Full_Name: JW
> Version: 2.4.47
> OS: Linux (Fedora 29, x86_64, fully patched)
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (151.196.22.177)
>
>
> I added -fsanitize=undefined to CFLAGS.
Hello,
In this case, the compiler is the problem. LMDB is 100% correct regarding
alignment on all supported CPUs (which is most of them). The x86 family
fully supports unaligned access, so LMDB makes use of this. On other CPUs,
which do not support unaligned access (e.g., SPARC), LMDB doesn't use them.
This ITS will be closed.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Mike Hommey
Version:
OS: Linux
URL: https://github.com/glandium/lmdb/commit/3e9a0dfc718699671ac2f21d40ef259b5da…
Submission from: (NULL) (153.194.155.35)
asm/cachectl.h doesn't contain the function declaration for cacheflush, but
sys/cachectl.h does. Having the declaration in mdb.c can cause linkage issues
when using things like -fvisibility=hidden.
--On Wednesday, June 05, 2019 7:53 PM +0000 Alexey Dubovkin
<adubovkin(a)linkedin.com> wrote:
> Thank you!
> Alexey
Hi Alexey,
As Howard already noted in his response to the ITS, there is no
demonstrated bug here. It would appear you've run out of free pages given
the mapsize you started with. As noted in the documentation, the general
expectation is one sets a very large mapsize from the start. Hope that
helps!
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>