From: Oleksandr Tymoshenko <ovt@google.com>
To: axboe@kernel.dk
Cc: asml.silence@gmail.com, io-uring@vger.kernel.org
Subject: [PATCH 0/2] Fix locking for MSG_RING and IOPOLL targets
Date: Tue, 22 Aug 2023 20:54:24 +0000 [thread overview]
Message-ID: <20230822205425.1385767-1-ovt@google.com> (raw)
In-Reply-To: <20230119180225.466835-1-axboe@kernel.dk>
Hello,
Does this patchset need to be backported to 6.1?
Thank you
next prev parent reply other threads:[~2023-08-22 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 18:02 [PATCH 0/2] Fix locking for MSG_RING and IOPOLL targets Jens Axboe
2023-01-19 18:02 ` [PATCH 1/2] io_uring/msg_ring: move double lock/unlock helpers higher up Jens Axboe
2023-01-19 18:02 ` [PATCH 2/2] io_uring/msg_ring: fix missing lock on overflow for IOPOLL Jens Axboe
2023-08-22 20:54 ` Oleksandr Tymoshenko [this message]
2023-08-22 22:19 ` [PATCH 0/2] Fix locking for MSG_RING and IOPOLL targets Gabriel Krisman Bertazi
2023-08-22 23:30 ` Jens Axboe
2023-08-23 0:06 ` 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=20230822205425.1385767-1-ovt@google.com \
--to=ovt@google.com \
--cc=asml.silence@gmail.com \
--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).