From: Christian Brauner <brauner@kernel.org>
To: cem@kernel.org
Cc: Christian Brauner <brauner@kernel.org>,
jack@suse.cz, akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
linux-mm@kvack.org, djwong@kernel.org, hughd@google.com,
mcgrof@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH V6 0/7] shmem: Add user and group quota support for tmpfs
Date: Tue, 25 Jul 2023 19:33:43 +0200 [thread overview]
Message-ID: <20230725-brummen-fortbestand-1b4f727337dc@brauner> (raw)
In-Reply-To: <20230725144510.253763-1-cem@kernel.org>
On Tue, 25 Jul 2023 16:45:03 +0200, cem@kernel.org wrote:
> 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.
>
> [...]
Applied to the vfs.tmpfs branch of the vfs/vfs.git tree.
Patches in the vfs.tmpfs branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.tmpfs
[1/7] shmem: make shmem_inode_acct_block() return error
https://git.kernel.org/vfs/vfs/c/fd612a41ed54
[2/7] shmem: make shmem_get_inode() return ERR_PTR instead of NULL
https://git.kernel.org/vfs/vfs/c/91f1d62b97b4
[3/7] quota: Check presence of quota operation structures instead of ->quota_read and ->quota_write callbacks
https://git.kernel.org/vfs/vfs/c/641c3cdf05e0
[4/7] shmem: prepare shmem quota infrastructure
https://git.kernel.org/vfs/vfs/c/8286a5c8264a
[5/7] shmem: quota support
https://git.kernel.org/vfs/vfs/c/9a9f8f590f6d
[6/7] shmem: Add default quota limit mount options
https://git.kernel.org/vfs/vfs/c/fbf5fbc5ed0e
[7/7] shmem: fix quota lock nesting in huge hole handling
https://git.kernel.org/vfs/vfs/c/5da76f81c519
prev parent reply other threads:[~2023-07-25 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 14:45 cem
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 ` Christian Brauner [this message]
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=20230725-brummen-fortbestand-1b4f727337dc@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=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 \
--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