From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/3] io-wq: add support for inheriting ->fs
Date: Tue, 11 Feb 2020 03:31:49 +0000 [thread overview]
Message-ID: <20200211033150.60A3120661@mail.kernel.org> (raw)
In-Reply-To: <20200209171113.14270-2-axboe@kernel.dk>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 5.3+
The bot has tested the following trees: v5.5.2, v5.4.18.
v5.5.2: Failed to apply! Possible dependencies:
05f3fb3c5397 ("io_uring: avoid ring quiesce for fixed file set unregister and update")
15b71abe7b52 ("io_uring: add support for IORING_OP_OPENAT")
66f4af93da57 ("io_uring: add support for probing opcodes")
b5dba59e0cf7 ("io_uring: add support for IORING_OP_CLOSE")
d3656344fea0 ("io_uring: add lookup table for various opcode needs")
d63d1b5edb7b ("io_uring: add support for fallocate()")
eddc7ef52a6b ("io_uring: add support for IORING_OP_STATX")
f86cd20c9454 ("io_uring: fix linked command file table usage")
v5.4.18: Failed to apply! Possible dependencies:
561fb04a6a22 ("io_uring: replace workqueue usage with io-wq")
771b53d033e8 ("io-wq: small threadpool implementation for io_uring")
ba5290ccb6b5 ("io_uring: replace s->needs_lock with s->in_async")
ba816ad61fdf ("io_uring: run dependent links inline if possible")
c5def4ab8494 ("io-wq: add support for bounded vs unbunded work")
c826bd7a743f ("io_uring: add set of tracing events")
fcb323cc53e2 ("io_uring: io_uring: add support for async work inheriting files")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-11 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 17:11 [PATCHSET v2] io_uring: Allow relative lookups Jens Axboe
2020-02-09 17:11 ` [PATCH 1/3] io-wq: add support for inheriting ->fs Jens Axboe
2020-02-11 3:31 ` Sasha Levin [this message]
2020-02-09 17:11 ` [PATCH 2/3] io_uring: grab ->fs as part of async preparation Jens Axboe
2020-02-11 3:31 ` Sasha Levin
2020-02-09 17:11 ` [PATCH 3/3] io_uring: allow AT_FDCWD for non-file openat/openat2/statx 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=20200211033150.60A3120661@mail.kernel.org \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=stable@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).