FAILED: patch "[PATCH] io_uring: honor original task RLIMIT_FSIZE" failed to apply to 5.4-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 4ed734b0d0913e566a9d871e15d24eb240f269f7 Mon Sep 17 00:00:00 2001
From: Jens Axboe <[email protected]>
Date: Fri, 20 Mar 2020 11:23:41 -0600
Subject: [PATCH] io_uring: honor original task RLIMIT_FSIZE
With the previous fixes for number of files open checking, I added some debug code to see if we had other spots where we're checking rlimit() against the async io-wq workers. The only one I found was file size checking, which we should also honor.
During write and fallocate prep, store the max file size and override that for the current ask if we're in io-wq worker context.
fs/io_uring.c +16 -1
@@ -604,7 +604,10 @@ struct io_kiocb {struct list_head list;unsigned int flags;refcount_t refs; -struct task_struct *task; +union { +struct task_struct *task; +unsigned long fsize; + };u64 user_data;u32 result;u32 sequence;
@@ -2593,6 +2596,8 @@ static int io_write_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe,if (unlikely (!(req->file->f_mode &FMODE_WRITE )))return -EBADF ; + req->fsize =rlimit (RLIMIT_FSIZE ); +/* either don't need iovec imported or already have it */ if (!req->io || req->flags &REQ_F_NEED_CLEANUP )return 0 ;
@@ -2662,10 +2667,17 @@ static int io_write(struct io_kiocb *req, bool force_nonblock) } kiocb->ki_flags |=IOCB_WRITE ; +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur = req->fsize; +if (req->file->f_op->write_iter) ret2 =call_write_iter (req->file, kiocb, &iter);else ret2 =loop_rw_iter (WRITE , req->file, kiocb, &iter); + +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur =RLIM_INFINITY ; +/* * Raw bdev writes will -EOPNOTSUPP for IOCB_NOWAIT. Just * retry them without IOCB_NOWAIT.
@@ -2848,8 +2860,10 @@ static void __io_fallocate(struct io_kiocb *req) {int ret; + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur = req->fsize; ret =vfs_fallocate (req->file, req->sync.mode, req->sync.off, req->sync.len); + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur =RLIM_INFINITY ;if (ret <0 )req_set_fail_links (req);io_cqring_add_event (req, ret);
@@ -2875,6 +2889,7 @@ static int io_fallocate_prep(struct io_kiocb *req, req->sync.off =READ_ONCE (sqe->off); req->sync.len =READ_ONCE (sqe->addr); req->sync.mode =READ_ONCE (sqe->len); + req->fsize =rlimit (RLIMIT_FSIZE );return 0 ; }
Quoted 5 lines · On 4/14/20 6:20 AM, [email protected] wrote:
The patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
Here's a 5.4 backport.
From 4ed734b0d0913e566a9d871e15d24eb240f269f7 Mon Sep 17 00:00:00 2001
From: Jens Axboe <[email protected]>
Date: Fri, 20 Mar 2020 11:23:41 -0600
Subject: [PATCH] io_uring: honor original task RLIMIT_FSIZE
With the previous fixes for number of files open checking, I added some debug code to see if we had other spots where we're checking rlimit() against the async io-wq workers. The only one I found was file size checking, which we should also honor.
During write and fallocate prep, store the max file size and override that for the current ask if we're in io-wq worker context.
fs/io_uring.c +10 -0
@@ -331,6 +331,7 @@ struct io_kiocb {#define REQ_F_ISREG 2048/* regular file */ #define REQ_F_MUST_PUNT 4096/* must be punted even for NONBLOCK */ #define REQ_F_TIMEOUT_NOSEQ 8192/* no timeout sequence */ +unsigned long fsize;u64 user_data;u32 result;u32 sequence;
@@ -1404,6 +1405,8 @@ static int io_read(struct io_kiocb *req, const struct sqe_submit *s,size_t iov_count;ssize_t read_size, ret; + req->fsize =rlimit (RLIMIT_FSIZE ); + ret =io_prep_rw (req, s, force_nonblock);if (ret)return ret;
@@ -1513,10 +1516,17 @@ static int io_write(struct io_kiocb *req, const struct sqe_submit *s, } kiocb->ki_flags |=IOCB_WRITE ; +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur = req->fsize; +if (file->f_op->write_iter) ret2 =call_write_iter (file, kiocb, &iter);else ret2 =loop_rw_iter (WRITE , file, kiocb, &iter); + +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur =RLIM_INFINITY ; +if (!force_nonblock || ret2 != -EAGAIN ) {io_rw_done (kiocb, ret2); }else {
Signature · 1 line
Jens Axboe
Quoted 8 lines · Jens Axboe
Quoted 5 lines · On 4/14/20 6:20 AM, [email protected] wrote:
The patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.Here's a 5.4 backport.
Sorry, please use this one!
From 4ed734b0d0913e566a9d871e15d24eb240f269f7 Mon Sep 17 00:00:00 2001
From: Jens Axboe <[email protected]>
Date: Fri, 20 Mar 2020 11:23:41 -0600
Subject: [PATCH] io_uring: honor original task RLIMIT_FSIZE
With the previous fixes for number of files open checking, I added some debug code to see if we had other spots where we're checking rlimit() against the async io-wq workers. The only one I found was file size checking, which we should also honor.
During write and fallocate prep, store the max file size and override that for the current ask if we're in io-wq worker context.
fs/io_uring.c +11 -0
@@ -331,6 +331,7 @@ struct io_kiocb {#define REQ_F_ISREG 2048/* regular file */ #define REQ_F_MUST_PUNT 4096/* must be punted even for NONBLOCK */ #define REQ_F_TIMEOUT_NOSEQ 8192/* no timeout sequence */ +unsigned long fsize;u64 user_data;u32 result;u32 sequence;
@@ -1085,6 +1086,9 @@ static int io_prep_rw(struct io_kiocb *req, const struct sqe_submit *s,if (S_ISREG (file_inode (req->file)->i_mode)) req->flags |=REQ_F_ISREG ; +if (force_nonblock) + req->fsize =rlimit (RLIMIT_FSIZE ); +/* * If the file doesn't support async, mark it as REQ_F_MUST_PUNT so * we know to async punt it even if it was opened O_NONBLOCK
@@ -1504,10 +1508,17 @@ static int io_write(struct io_kiocb *req, const struct sqe_submit *s, } kiocb->ki_flags |=IOCB_WRITE ; +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur = req->fsize; +if (file->f_op->write_iter) ret2 =call_write_iter (file, kiocb, &iter);else ret2 =loop_rw_iter (WRITE , file, kiocb, &iter); + +if (!force_nonblock) + current->signal->rlim[RLIMIT_FSIZE ].rlim_cur =RLIM_INFINITY ; +if (!force_nonblock || ret2 != -EAGAIN ) {io_rw_done (kiocb, ret2); }else {
Signature · 1 line
Jens Axboe
Greg KH
maintainerQuoted 11 lines · Jens Axboe
Quoted 8 lines · Jens Axboe
Quoted 5 lines · On 4/14/20 6:20 AM, [email protected] wrote:
The patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.Here's a 5.4 backport.
Sorry, please use this one!
Now queued up, along with the other backports, thanks!
greg k-h
Quoted 9 lines · Greg KH
Quoted 8 lines · Jens Axboe
Quoted 7 lines · Jens Axboe
Quoted 5 lines · On 4/14/20 6:20 AM, [email protected] wrote:
The patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Here's a 5.4 backport.
Sorry, please use this one!
Now queued up, along with the other backports, thanks!
Thanks Greg!
Signature · 1 line
Jens Axboe