From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>,
Christian Brauner <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 6.8-rc1
Date: Wed, 10 Jan 2024 11:13:50 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/8/24 11:24 AM, Jens Axboe wrote:
> Also note that this will throw a merge conflict with the block branch,
> as we killed the IORING_URING_CMD_POLLED flag and associated cookie in
> struct io_uring_cmd, and this branch moved those things to a different
> file. The resolution is to remove all of the offending hunk in
> include/linux/io_uring.h and then edit include/linux/io_uring/cmd.h,
> killing IORING_URING_CMD_POLLED in there and getting rid of the union
> and cookie field in struct io_uring_cmd. Including my resolution of the
> merge at the end of the email.
Forgot to mention the security conflict too, which I was reminded of when
that landed upstream. See:
https://lore.kernel.org/lkml/[email protected]/
for the simple fix.
--
Jens Axboe
next prev parent reply other threads:[~2024-01-10 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:24 [GIT PULL] io_uring updates for 6.8-rc1 Jens Axboe
2024-01-10 18:13 ` Jens Axboe [this message]
2024-01-11 22:57 ` pr-tracker-bot
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] \
[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