From: "John Ericson" <mail@johnericson.me>
To: "Cong Wang" <cwang@multikernel.io>
Cc: "Li Chen" <me@linux.beauty>, "Andy Lutomirski" <luto@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
"Jens Axboe" <axboe@kernel.dk>,
"network dev" <netdev@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC] connectat()/bindat() or an alternative design
Date: Wed, 01 Jul 2026 15:41:39 -0400 [thread overview]
Message-ID: <d0999427-dc53-4f8b-8026-c7d97cb31cae@app.fastmail.com> (raw)
In-Reply-To: <e396ce86-ec84-4189-9da2-98af7cfa6c41@app.fastmail.com>
Two small addendums to my previous email:
First, I linked these two unresponded-to emails for prior art in the
opening email of the thread:
> https://lore.kernel.org/netdev/4FCF171B.8000207@parallels.com/
> https://lore.kernel.org/all/CAEnbY+co6YLXANfeMnfBOBs8Ba_Sbdqz0Ahm8RzAhRF7MrxL4Q@mail.gmail.com/
Since then, I found one more:
https://lore.kernel.org/all/20120815161141.7598.16682.stgit@localhost.localdomain/#t
which is an actual patch by the same person that wrote the first linked
email, with replies. Hopefully that is useful.
Second, it occurred to me that regarding
> (Maybe `bind_unix_anon` should furthermore `listen` right away on
> `lfd` too?)
a useful thing to first decide is whether `bind_unix_anon` is
helpful and/or should be allowed for `SOCK_DGRAM`.
John
next prev parent reply other threads:[~2026-07-01 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 19:09 [RFC] connectat()/bindat() or an alternative design John Ericson
2026-06-08 19:45 ` Cong Wang
2026-06-11 2:08 ` John Ericson
2026-06-12 18:50 ` Cong Wang
2026-06-23 17:40 ` John Ericson
2026-06-30 20:22 ` John Ericson
2026-07-01 19:41 ` John Ericson [this message]
2026-07-02 0:32 ` Cong Wang
2026-07-02 3:22 ` John Ericson
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=d0999427-dc53-4f8b-8026-c7d97cb31cae@app.fastmail.com \
--to=mail@johnericson.me \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cwang@multikernel.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=me@linux.beauty \
--cc=netdev@vger.kernel.org \
/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