From: Carlos Maiolino <cem@kernel.org>
To: hughd@google.com, jack@suse.cz, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH V4 0/6] shmem: Add user and group quota support for tmpfs
Date: Mon, 15 May 2023 10:54:39 +0200 [thread overview]
Message-ID: <20230515085439.5s5n4xxljgl6e5jl@andromeda> (raw)
In-Reply-To: <20230426102008.2930932-1-cem@kernel.org>
On Wed, Apr 26, 2023 at 12:20:02PM +0200, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> Hello folks.
>
> This is the final version of the quota support from tmpfs, with all the issues
> addressed, and now including RwB tags on all patches, and should be ready for
> merge. Details are within each patch, and the original cover-letter below.
>
Ping? Can somebody manage to pickup these patches?
Thanks!
> Hi folks. this work has been done originally by Lukas, but he left the company,
> so I'm taking over his work from where he left it of. This series is virtually
> done, and he had updated it with comments from the last version, but, I'm
> initially posting it as a RFC because it's been a while since he posted the
> last version.
> Most of what I did here was rebase his last work on top of current Linus's tree.
>
> Honza, there is one patch from you in this series, which I believe you had it
> suggested to Lukas on a previous version.
>
> The original cover-letter follows...
>
> people have been asking for quota support in tmpfs many times in the past
> mostly to avoid one malicious user, or misbehaving user/program to consume
> all of the system memory. This has been partially solved with the size
> mount option, but some problems still prevail.
>
> One of the problems is the fact that /dev/shm is still generally unprotected
> with this and another is administration overhead of managing multiple tmpfs
> mounts and lack of more fine grained control.
>
> Quota support can solve all these problems in a somewhat standard way
> people are already familiar with from regular file systems. It can give us
> more fine grained control over how much memory user/groups can consume.
> Additionally it can also control number of inodes and with special quota
> mount options introduced with a second patch we can set global limits
> allowing us to replace the size mount option with quota entirely.
>
> Currently the standard userspace quota tools (quota, xfs_quota) are only
> using quotactl ioctl which is expecting a block device. I patched quota [1]
> and xfs_quota [2] to use quotactl_fd in case we want to run the tools on
> mount point directory to work nicely with tmpfs.
>
> The implementation was tested on patched version of xfstests [3].
>
> [1] https://github.com/lczerner/quota/tree/quotactl_fd_support
> [2] https://github.com/lczerner/xfsprogs/tree/quotactl_fd_support
> [3] https://github.com/lczerner/xfstests/tree/tmpfs_quota_support
>
>
> Jan Kara (1):
> quota: Check presence of quota operation structures instead of
> ->quota_read and ->quota_write callbacks
>
> Lukas Czerner (5):
> shmem: make shmem_inode_acct_block() return error
> shmem: make shmem_get_inode() return ERR_PTR instead of NULL
> shmem: prepare shmem quota infrastructure
> shmem: quota support
> Add default quota limit mount options
>
> Documentation/filesystems/tmpfs.rst | 31 ++
> fs/Kconfig | 12 +
> fs/quota/dquot.c | 2 +-
> include/linux/shmem_fs.h | 28 ++
> include/uapi/linux/quota.h | 1 +
> mm/Makefile | 2 +-
> mm/shmem.c | 465 +++++++++++++++++++++-------
> mm/shmem_quota.c | 350 +++++++++++++++++++++
> 8 files changed, 783 insertions(+), 108 deletions(-)
> create mode 100644 mm/shmem_quota.c
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> --
> 2.30.2
>
--
Carlos Maiolino
next prev parent reply other threads:[~2023-05-15 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p9LagXdw-LiFcxInjRmJLqLkzLqVNNSLD3tgGy8JvvgCPGI7k-7Aaxu5gpTG0Kyy3tXWAbNZT8ZUzAH1eFW4qw==@protonmail.internalid>
2023-04-26 10:20 ` cem
2023-04-26 10:20 ` [PATCH 1/6] shmem: make shmem_inode_acct_block() return error cem
2023-04-26 10:20 ` [PATCH 2/6] shmem: make shmem_get_inode() return ERR_PTR instead of NULL cem
2023-04-26 10:20 ` [PATCH 3/6] quota: Check presence of quota operation structures instead of ->quota_read and ->quota_write callbacks cem
2023-04-26 10:20 ` [PATCH 4/6] shmem: prepare shmem quota infrastructure cem
2023-04-26 10:20 ` [PATCH 5/6] shmem: quota support cem
2023-04-26 10:20 ` [PATCH 6/6] Add default quota limit mount options cem
2023-05-15 8:54 ` Carlos Maiolino [this message]
2023-05-17 10:50 ` [PATCH V4 0/6] shmem: Add user and group quota support for tmpfs Hugh Dickins
2023-05-17 12:22 ` Carlos Maiolino
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=20230515085439.5s5n4xxljgl6e5jl@andromeda \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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