From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>,
"[email protected]" <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.6-rc
Date: Sat, 21 Mar 2020 12:38:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Two different fixes in here:
- Fix for a potential NULL pointer deref for links with async or drain
marked (Pavel)
- Fix for not properly checking RLIMIT_NOFILE for async punted
operations. This affects openat/openat2, which were added this cycle,
and accept4. I did a full audit of other cases where we might check
current->signal->rlim[] and found only RLIMIT_FSIZE for buffered
writes and fallocate. That one is fixed and queued for 5.7 and marked
stable.
Please pull!
git://git.kernel.dk/linux-block.git tags/io_uring-5.6-20200320
----------------------------------------------------------------
Jens Axboe (2):
io_uring: make sure openat/openat2 honor rlimit nofile
io_uring: make sure accept honor rlimit nofile
Pavel Begunkov (1):
io_uring: NULL-deref for IOSQE_{ASYNC,DRAIN}
fs/file.c | 7 ++++++-
fs/io_uring.c | 18 ++++++++++++++++--
include/linux/file.h | 1 +
include/linux/socket.h | 3 ++-
net/socket.c | 8 +++++---
5 files changed, 30 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-03-21 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 18:38 Jens Axboe [this message]
2020-03-21 19:15 ` [GIT PULL] io_uring fixes for 5.6-rc pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-03-13 17:50 Jens Axboe
2020-03-13 20:18 ` Linus Torvalds
2020-03-13 20:33 ` Paul E. McKenney
2020-03-13 21:33 ` Jens Axboe
2020-03-13 20:25 ` pr-tracker-bot
2020-03-07 19:16 Jens Axboe
2020-03-07 20:25 ` pr-tracker-bot
2020-02-28 18:42 Jens Axboe
2020-02-28 19:55 ` 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