From: Jens Axboe <axboe@kernel.dk>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, io-uring@vger.kernel.org,
Pavel Begunkov <asml.silence@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] io_uring: Fix return value from alloc_fixed_file_ref_node
Date: Wed, 6 Jan 2021 09:20:43 -0700 [thread overview]
Message-ID: <7facda23-3c3d-473d-9ec6-c58cbc1ea6de@kernel.dk> (raw)
In-Reply-To: <20210106160926.593770-1-willy@infradead.org>
On 1/6/21 9:09 AM, Matthew Wilcox (Oracle) wrote:
> alloc_fixed_file_ref_node() currently returns an ERR_PTR on failure.
> io_sqe_files_unregister() expects it to return NULL and since it can only
> return -ENOMEM, it makes more sense to change alloc_fixed_file_ref_node()
> to behave that way.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-01-06 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 16:09 [PATCH] io_uring: Fix return value from alloc_fixed_file_ref_node Matthew Wilcox (Oracle)
2021-01-06 16:20 ` 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=7facda23-3c3d-473d-9ec6-c58cbc1ea6de@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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).