From: Pavel Begunkov <asml.silence@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
Yejune Deng <yejune.deng@gmail.com>
Cc: viro@zeniv.linux.org.uk, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring: remove io_remove_personalities()
Date: Wed, 23 Dec 2020 12:41:39 +0000 [thread overview]
Message-ID: <3c013151-37de-1ef0-e989-9f871665d650@gmail.com> (raw)
In-Reply-To: <20201223103623.mxjsmitdmqsx6ftd@steredhat>
On 23/12/2020 10:36, Stefano Garzarella wrote:
> On Wed, Dec 23, 2020 at 11:27:05AM +0800, Yejune Deng wrote:
>> The function io_remove_personalities() is very similar to
>> io_unregister_personality(),but the latter has a more reasonable
>> return value.
>>
>> Signed-off-by: Yejune Deng <yejune.deng@gmail.com>
>> ---
>> fs/io_uring.c | 25 ++++++-------------------
>> 1 file changed, 6 insertions(+), 19 deletions(-)
>
> The patch LGTM, maybe as an alternative you can leave io_remove_personality() with the interface needed by idr_for_each() and implement io_unregister_personality() calling io_remove_personality() with the right parameters.
Right, don't replace sane types with void * just because.
Leave well-typed io_unregister_personality() and call it from
io_remove_personalities().
Also
* idr_for_each() - Iterate through all stored pointers.
...
* If @fn returns anything other than %0, the iteration stops and that
* value is returned from this function.
For io_remove_personality() iod==NULL should not happen because
it's under for_each and synchronised, but leave the return value be
io_remove_personality(void *, ...)
{
struct io_ring_ctx *ctx = data;
io_unregister_personality(ctx, id);
return 0;
}
--
Pavel Begunkov
next prev parent reply other threads:[~2020-12-23 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 3:27 [PATCH] io_uring: remove io_remove_personalities() Yejune Deng
2020-12-23 10:36 ` Stefano Garzarella
2020-12-23 12:41 ` Pavel Begunkov [this message]
2020-12-24 1:38 ` Yejune Deng
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=3c013151-37de-1ef0-e989-9f871665d650@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yejune.deng@gmail.com \
/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