From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET v2 0/2] io_uring: ensure we inherit task creds
Date: Mon, 25 Nov 2019 09:52:32 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
(resend as v1 included a 5.4 backport by accident)
As referenced in patch #2, fuse + fsync fails with aio because of the
async punt of fsync not inheriting the original task creds. Apply the
same sort of fix for io_uring, and apply it globally to all requests
so we ensure we always present the rights creds when offloaded.
fs/io-wq.c | 24 ++++++++++++++++--------
fs/io-wq.h | 13 ++++++++++---
fs/io_uring.c | 23 +++++++++++++++++++++--
3 files changed, 47 insertions(+), 13 deletions(-)
--
Jens Axboe
next reply other threads:[~2019-11-25 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 16:52 Jens Axboe [this message]
2019-11-25 16:52 ` [PATCH 1/2] io-wq: have io_wq_create() take a 'data' argument Jens Axboe
2019-11-25 16:52 ` [PATCH 2/2] io_uring: async workers should inherit the user creds 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] \
/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