From: Dmitry Safonov <0x7f454c46@gmail.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] fs/pipe: use kvcalloc to allocate a pipe_buffer array
Date: Thu, 6 Jan 2022 17:37:03 +0000 [thread overview]
Message-ID: <cbe26979-15cd-a460-7f9d-6035f8862073@gmail.com> (raw)
In-Reply-To: <20220104171058.22580-1-avagin@gmail.com>
On 1/4/22 17:10, Andrei Vagin wrote:
> Right now, kcalloc is used to allocate a pipe_buffer array. The size of
> the pipe_buffer struct is 40 bytes. kcalloc allows allocating reliably
> chunks with sizes less or equal to PAGE_ALLOC_COSTLY_ORDER (3). It means
> that the maximum pipe size is 3.2MB in this case.
>
> In CRIU, we use pipes to dump processes memory. CRIU freezes a target
> process, injects a parasite code into it and then this code splices
> memory into pipes. If a maximum pipe size is small, we need to
> do many iterations or create many pipes.
>
> kvcalloc attempt to allocate physically contiguous memory, but upon
> failure, fall back to non-contiguous (vmalloc) allocation and so it
> isn't limited by PAGE_ALLOC_COSTLY_ORDER.
>
> The maximum pipe size for non-root users is limited by
> the /proc/sys/fs/pipe-max-size sysctl that is 1MB by default, so only
> the root user will be able to trigger vmalloc allocations.
>
> Cc: Dmitry Safonov <0x7f454c46@gmail.com>
> Signed-off-by: Andrei Vagin <avagin@gmail.com>
Reviewed-by: Dmitry Safonov <0x7f454c46@gmail.com>
> ---
> fs/pipe.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/fs/pipe.c b/fs/pipe.c
> index 6d4342bad9f1..45565773ec33 100644
> --- a/fs/pipe.c
> +++ b/fs/pipe.c
> @@ -802,7 +802,7 @@ struct pipe_inode_info *alloc_pipe_info(void)
> if (too_many_pipe_buffers_hard(user_bufs) && pipe_is_unprivileged_user())
> goto out_revert_acct;
>
> - pipe->bufs = kcalloc(pipe_bufs, sizeof(struct pipe_buffer),
> + pipe->bufs = kvcalloc(pipe_bufs, sizeof(struct pipe_buffer),
> GFP_KERNEL_ACCOUNT);
>
> if (pipe->bufs) {
> @@ -845,7 +845,7 @@ void free_pipe_info(struct pipe_inode_info *pipe)
> }
> if (pipe->tmp_page)
> __free_page(pipe->tmp_page);
> - kfree(pipe->bufs);
> + kvfree(pipe->bufs);
> kfree(pipe);
> }
>
> @@ -1260,8 +1260,7 @@ int pipe_resize_ring(struct pipe_inode_info *pipe, unsigned int nr_slots)
> if (nr_slots < n)
> return -EBUSY;
>
> - bufs = kcalloc(nr_slots, sizeof(*bufs),
> - GFP_KERNEL_ACCOUNT | __GFP_NOWARN);
> + bufs = kvcalloc(nr_slots, sizeof(*bufs), GFP_KERNEL_ACCOUNT);
> if (unlikely(!bufs))
> return -ENOMEM;
>
> @@ -1288,7 +1287,7 @@ int pipe_resize_ring(struct pipe_inode_info *pipe, unsigned int nr_slots)
> head = n;
> tail = 0;
>
> - kfree(pipe->bufs);
> + kvfree(pipe->bufs);
> pipe->bufs = bufs;
> pipe->ring_size = nr_slots;
> if (pipe->max_usage > nr_slots)
Thanks,
Dmitry
next prev parent reply other threads:[~2022-01-06 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 17:10 Andrei Vagin
2022-01-05 6:54 ` Dmitry Safonov
2022-01-05 21:47 ` Andrei Vagin
2022-01-05 22:50 ` Dmitry Safonov
2022-01-06 17:37 ` Dmitry Safonov [this message]
2022-01-25 3:21 ` Andrei Vagin
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=cbe26979-15cd-a460-7f9d-6035f8862073@gmail.com \
--to=0x7f454c46@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome