From: patchwork-bot+netdevbpf@kernel•org
To: Pavel Begunkov <asml.silence@gmail•com>
Cc: io-uring@vger•kernel.org, axboe@kernel•dk, jannh@google•com,
davem@davemloft•net, kuba@kernel•org, edumazet@google•com,
pabeni@redhat•com, netdev@vger•kernel.org
Subject: Re: [PATCH RESEND] io_uring/af_unix: disable sending io_uring over sockets
Date: Sat, 09 Dec 2023 21:30:23 +0000 [thread overview]
Message-ID: <170215742325.28655.3532464326317595709.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c716c88321939156909cfa1bd8b0faaf1c804103.1701868795.git.asml.silence@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft•net>:
On Wed, 6 Dec 2023 13:55:19 +0000 you wrote:
> File reference cycles have caused lots of problems for io_uring
> in the past, and it still doesn't work exactly right and races with
> unix_stream_read_generic(). The safest fix would be to completely
> disallow sending io_uring files via sockets via SCM_RIGHT, so there
> are no possible cycles invloving registered files and thus rendering
> SCM accounting on the io_uring side unnecessary.
>
> [...]
Here is the summary with links:
- [RESEND] io_uring/af_unix: disable sending io_uring over sockets
https://git.kernel.org/netdev/net/c/69db702c8387
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-09 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 13:55 [PATCH RESEND] io_uring/af_unix: disable sending io_uring over sockets Pavel Begunkov
2023-12-09 1:40 ` Jakub Kicinski
2023-12-09 21:30 ` patchwork-bot+netdevbpf [this message]
2023-12-10 1:18 ` Pavel Begunkov
2023-12-12 2:39 ` Jakub Kicinski
2023-12-12 4:45 ` 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=170215742325.28655.3532464326317595709.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=asml.silence@gmail$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=io-uring@vger$(echo .)kernel.org \
--cc=jannh@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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