io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Metzmacher <metze@samba.org>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCHSET 0/4] Allow relative lookups
Date: Fri, 7 Feb 2020 22:56:42 +0100	[thread overview]
Message-ID: <36ca4e5a-9ac9-2bc6-a2e6-f3e2667463c9@samba.org> (raw)
In-Reply-To: <20200207155039.12819-1-axboe@kernel.dk>


[-- Attachment #1.1: Type: text/plain, Size: 659 bytes --]

Hi Jens,

Am 07.02.20 um 16:50 schrieb Jens Axboe:
> Due to an oversight on my part, AT_FDCWD lookups only work when the
> lookup can be done inline, not async. This patchset rectifies that,
> aiming for 5.6 for this one as it would be a shame to have openat etc
> without that.
> 
> Just 3 small simple patches - grab the task ->fs, add io-wq suppor for
> passing it in and setting it, and finally add a ->needs_fs to the opcode
> table list of requirements for openat/openat2/statx.
> 
> Last patch just ensures we allow AT_FDCWD.

Thanks! But IOSQE_FIXED_FILE is still not supported and not rejected at
the same time, correct?

metze



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-02-07 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 15:50 [PATCHSET 0/4] Allow relative lookups Jens Axboe
2020-02-07 15:50 ` [PATCH 1/4] io_uring: grab owning task fs_struct Jens Axboe
2020-02-07 15:50 ` [PATCH 2/4] io-wq: add support for inheriting ->fs Jens Axboe
2020-02-07 15:50 ` [PATCH 3/4] io_uring: add ->needs_fs to the opcode requirements table Jens Axboe
2020-02-07 15:50 ` [PATCH 4/4] io_uring: allow AT_FDCWD for non-file openat/openat2/statx Jens Axboe
2020-02-07 21:56 ` Stefan Metzmacher [this message]
2020-02-07 22:47   ` [PATCHSET 0/4] Allow relative lookups Jens Axboe
2020-02-07 22:56     ` Stefan Metzmacher
2020-02-07 23:07       ` Stefan Metzmacher
2020-02-08 20:05       ` 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 \
    --in-reply-to=36ca4e5a-9ac9-2bc6-a2e6-f3e2667463c9@samba.org \
    --to=metze@samba.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@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).