public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Stefan Metzmacher <[email protected]>, Jens Axboe <[email protected]>,
	[email protected]
Subject: Re: [PATCH 5.11] io_uring: don't take fs for recvmsg/sendmsg
Date: Sat, 7 Nov 2020 16:07:25 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 07/11/2020 16:02, Pavel Begunkov wrote:
> On 07/11/2020 13:46, Stefan Metzmacher wrote:
>> Hi Pavel,
>>
>>> We don't even allow not plain data msg_control, which is disallowed in __sys_{send,revb}msg_sock().
>>
>> Can't we better remove these checks and allow msg_control?
>> For me it's a limitation that I would like to be removed.
> 
> We can grab fs only in specific situations as you mentioned, by e.g.
> adding a switch(opcode) in io_prep_async_work(), but that's the easy
> part. All msg_control should be dealt one by one as they do different
> things. And it's not the fact that they ever require fs.

BTW, Jens mentioned that there is a queued patch that allows plain
data msg_control. Are those not enough?

> 
>>
>> If there's a cost using IO_WQ_WORK_FS, would it be possible to use IO_WQ_WORK_FS only it msg_control is actually use> 
>>   if (msg->msg_control || msg->msg_controllen) 
>>       static const struct io_op_def sendmsg_control_op_def = {
>>          ...
>>       };
>>
>>       something = &sendmsg_control_op_def;
>>   }
> 

-- 
Pavel Begunkov

  reply	other threads:[~2020-11-07 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07 13:20 [PATCH 5.11] io_uring: don't take fs for recvmsg/sendmsg Pavel Begunkov
2020-11-07 13:46 ` Stefan Metzmacher
2020-11-07 16:02   ` Pavel Begunkov
2020-11-07 16:07     ` Pavel Begunkov [this message]
2020-11-18 16:27       ` Stefan Metzmacher
2020-11-18 16:57         ` Stefan Metzmacher
2020-11-18 19:50           ` Pavel Begunkov
2020-11-19  9:17             ` Stefan Metzmacher
2020-11-15 13:07 ` Pavel Begunkov
2020-11-16 16:31 ` Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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