From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jann Horn <jannh@google.com>,
Andreas Smas <andreas@lonelycoder.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
io-uring <io-uring@vger.kernel.org>
Subject: Re: io_uring, IORING_OP_RECVMSG and ancillary data
Date: Mon, 27 Apr 2020 14:13:18 -0600 [thread overview]
Message-ID: <a16d1b24-454e-f96a-4faa-23f68ecaaa6b@kernel.dk> (raw)
In-Reply-To: <20200427201043.GA6292@infradead.org>
On 4/27/20 2:10 PM, Christoph Hellwig wrote:
> On Mon, Apr 27, 2020 at 02:08:25PM -0600, Jens Axboe wrote:
>> Possibly... Totally untested, maybe I forgot to mention that :-)
>> I'll check.
>>
>> The question was more "in principle" if this was a viable approach. The
>> whole cmsg_type and cmsg_level is really a mess.
>
> FYI, I have a series in the works to sort out the set_fs and
> casting to/from __user mess around msg_control. It needs a little
> more work, but hopefully I can find some time the next days.
That'd be great - looking at it right now, I'd need to refactor
____sys_sendmsg (and ditto receive side) to poke at cmsg before
allowing us to proceed. I'll wait for you to post your series and
base it on top of that, if appropriate.
--
Jens Axboe
prev parent reply other threads:[~2020-04-27 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 17:29 io_uring, IORING_OP_RECVMSG and ancillary data Andreas Smas
2020-04-25 20:23 ` Jens Axboe
2020-04-27 19:20 ` Jann Horn
2020-04-27 19:29 ` Jens Axboe
2020-04-27 19:53 ` Jens Axboe
2020-04-27 20:03 ` Jann Horn
2020-04-27 20:08 ` Jens Axboe
2020-04-27 20:10 ` Christoph Hellwig
2020-04-27 20:13 ` Jens Axboe [this message]
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=a16d1b24-454e-f96a-4faa-23f68ecaaa6b@kernel.dk \
--to=axboe@kernel.dk \
--cc=andreas@lonelycoder.com \
--cc=hch@infradead.org \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).