From: cem@kernel.org
To: linux-fsdevel@vger.kernel.org
Cc: jack@suse.cz, akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
linux-mm@kvack.org, djwong@kernel.org, hughd@google.com,
brauner@kernel.org, mcgrof@kernel.org
Subject: [PATCH V6 0/7] shmem: Add user and group quota support for tmpfs
Date: Tue, 25 Jul 2023 16:45:03 +0200 [thread overview]
Message-ID: <20230725144510.253763-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cem@kernel.org>
Hello folks.
This is a new version of the implementation of tmpfs quota, below is the serie's
changelog, hopefully it make it easier to track down changes done on the past 3
versions.
I've rebased this series on Linus today's TOT, hopefully it prevents conflicts.
I also removed Jan Kara's RwB from patch 4, due to changes in functions
definition.
Changelog:
V6:
- Fix build warning (patch 4) by defining shmem_mark_dquot_dirty() and
shmem_dquot_write_info() as static functions
- Add a patch to fix syzkaller's reports.
Once Patch 7 is applied, I didn't manage to reproduce the
syzkaller issues anymore, so, added a Tested-by: tag
V5:
- Update shmem_parse_one() to prevent quota enablement in unprivileged mounts.
V4:
- Rebase to fix conflicts against 'noswap' mount option.
Original cover below.
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
Carlos Maiolino (3):
shmem: make shmem_get_inode() return ERR_PTR instead of NULL
shmem: prepare shmem quota infrastructure
shmem: quota support
Hugh Dickins (1):
shmem: fix quota lock nesting in huge hole handling
Jan Kara (1):
quota: Check presence of quota operation structures instead of
->quota_read and ->quota_write callbacks
Lukas Czerner (2):
shmem: make shmem_inode_acct_block() return error
shmem: 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/huge_memory.c | 6 +-
mm/khugepaged.c | 13 +-
mm/shmem.c | 495 +++++++++++++++++++++-------
mm/shmem_quota.c | 350 ++++++++++++++++++++
10 files changed, 812 insertions(+), 128 deletions(-)
create mode 100644 mm/shmem_quota.c
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
--
2.39.2
next reply other threads:[~2023-07-25 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 14:45 cem [this message]
2023-07-25 14:45 ` [PATCH 1/7] shmem: make shmem_inode_acct_block() return error cem
2023-07-25 14:45 ` [PATCH 2/7] shmem: make shmem_get_inode() return ERR_PTR instead of NULL cem
2023-07-25 14:45 ` [PATCH 3/7] quota: Check presence of quota operation structures instead of ->quota_read and ->quota_write callbacks cem
2023-07-25 14:45 ` [PATCH 4/7] shmem: prepare shmem quota infrastructure cem
2023-08-01 21:37 ` Jan Kara
2023-08-02 7:53 ` Christian Brauner
2023-07-25 14:45 ` [PATCH 5/7] shmem: quota support cem
2023-07-25 14:45 ` [PATCH 6/7] shmem: Add default quota limit mount options cem
2023-07-25 14:45 ` [PATCH 7/7] shmem: fix quota lock nesting in huge hole handling cem
2023-07-25 17:33 ` [PATCH V6 0/7] shmem: Add user and group quota support for tmpfs Christian Brauner
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=20230725144510.253763-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@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 \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).