From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 0/7] various build fixes + OpenBSD compat, [PATCH 7/7] xap_helper.h: fix double-free on OpenBSD hdestroy
Date: Wed, 30 Aug 2023 21:18:49 +0000 [thread overview]
Message-ID: <20230830211849.M275594@dcvr> (raw)
In-Reply-To: <20230830143409+0200.929541-stepnem@smrk.net>
Štěpán Němec <stepnem@smrk.net> wrote:
<snip> thanks for the additional notes.
> In any case, it does suck that OpenBSD is now the odd one out, but
> having no experience with the interface myself, I have no opinion on
> which behavior makes more sense.
Yeah, it's very limited and neglected interface that hardly
anybody uses; but it's all POSIX C offers. Most C projects end
up implementing their own hash table or importing something
well-known (Attractive Chaos khash, ccan, gnulib, etc...).
I intend to use rculfhash from Userspace-RCU for the lei FUSE
component. That'll likely be Linux-only since I can't bear
using FUSE without threads nor readdirplus (only in FUSE 3+)
when dealing with Maildirs. I don't think FUSE 3 support exists
outside of Linux, yet...
> Thanks for working on these (though I've had no complaints regarding the
> actual functionality I need on OpenBSD so far) and let me know if you
> want me to test something. (With cindex.t out of the way (says 'ok'
> now, plus a few W: reaped unknown PID), "make test" now gets stuck on
> lei-import-http.t for me (with or without this series; still the same
> test instance); I haven't seen kqnotify.t fail in the few runs I did.)
What's lei-import-http.t stuck on? I haven't seen that...
next prev parent reply other threads:[~2023-08-30 21:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 5:10 [PATCH 0/7] various build fixes + OpenBSD compat Eric Wong
2023-08-30 5:10 ` [PATCH 1/7] treewide: drop MSG_EOR with AF_UNIX+SOCK_SEQPACKET Eric Wong
2023-08-30 5:10 ` [PATCH 2/7] Makefile.PL: fix syntax for ASan and valgrind targets Eric Wong
2023-08-30 5:10 ` [PATCH 3/7] Makefile.PL: depend on autodie, at least for tests Eric Wong
2023-08-30 5:10 ` [PATCH 4/7] t/kqnotify: improve test reliability on OpenBSD Eric Wong
2023-08-30 5:10 ` [PATCH 5/7] xap_helper.h: don't compress debug sections " Eric Wong
2023-08-30 5:10 ` [PATCH 6/7] xap_helper.h: limit stderr assignment to glibc+FreeBSD Eric Wong
2023-08-30 5:10 ` [PATCH 7/7] xap_helper.h: fix double-free on OpenBSD hdestroy Eric Wong
2023-08-30 12:34 ` [PATCH 0/7] various build fixes + OpenBSD compat, " Štěpán Němec
2023-08-30 21:18 ` Eric Wong [this message]
2023-08-31 9:11 ` Štěpán Němec
2023-08-31 17:26 ` Štěpán Němec
2023-09-01 11:09 ` Eric Wong
2023-09-02 10:54 ` Štěpán Němec
2023-09-02 11:07 ` [PATCH v2] Clarify Inline::C dependency (optional on Linux, required elsewhere) Štěpán Němec
2023-09-02 18:50 ` Eric Wong
2023-09-02 19:08 ` Štěpán Němec
2023-09-02 19:44 ` Eric Wong
2023-09-02 20:45 ` Štěpán Němec
2023-09-02 20:56 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230830211849.M275594@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=stepnem@smrk.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).