From: Jens Axboe <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected],
Pavel Begunkov <[email protected]>,
Gabriel Krisman Bertazi <[email protected]>,
Tetsuo Handa <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] io_uring: Check socket is valid in io_bind()/io_listen()
Date: Sat, 13 Jul 2024 06:40:48 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sat, 13 Jul 2024 19:05:02 +0900, Tetsuo Handa wrote:
> We need to check that sock_from_file(req->file) != NULL.
>
>
Applied, thanks!
[1/1] io_uring: Check socket is valid in io_bind()/io_listen()
commit: ad00e629145b2b9f0d78aa46e204a9df7d628978
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-07-13 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 8:21 [syzbot] [io-uring] general protection fault in tomoyo_socket_bind_permission syzbot
2024-07-13 10:05 ` [PATCH] io_uring: Check socket is valid in io_bind()/io_listen() Tetsuo Handa
2024-07-13 12:38 ` Jens Axboe
2024-07-13 12:40 ` Jens Axboe [this message]
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=172087444804.7272.17982342612300126690.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[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