mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: YouYou Yu <youyouyu@amazon.com>
To: <jack@suse.cz>
Cc: <brauner@kernel.org>, <dgj@amazon.com>, <gunnarku@amazon.com>,
	<lichliu@redhat.com>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <viro@zeniv.linux.org.uk>,
	<youyouyu@amazon.com>
Subject: Re: [PATCH] quota: initialize dquot cache before mounting rootfs
Date: Tue, 20 Oct 2026 21:52:29 +0000	[thread overview]
Message-ID: <20261020215229.31406-1-youyouyu@amazon.com> (raw)
In-Reply-To: <4x3ngu2v723xnbommkln6yjwj27qdiy53dphxp74thsbihfqcr@rehvrhj7egvk>

Hi Jan,

Thanks for reviewing.

On Mon, 19 Oct 2026 12:44:49 +0200, Jan Kara wrote:
> I definitely don't think anybody sane wants quotas on initramfs. Is this
> just a fuzzing result or are you really interested in that functionality?

The truth is it's not a fuzzing result, we are really interested in it.
We run systems that extensively use rootfs and we want to limit per user
usage on it the same way tmpfs quotas allow on any other tmpfs mount.

> Instead of pulling quota into early boot I'd just refuse tmpfs mount in
> this case (same result as original behavior but clearer error message :)).

Refusing the mount would avoid the crash, but rootfs would then be
the only tmpfs instance where quotas can't be used, even though
initramfs_options= exists to pass mount options to it. That said, if
initializing this earlier is a concern, I'm happy to rework the patch
if you have a preferred approach.

Thanks,
YouYou

      reply	other threads:[~2026-10-20 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 18:36 YouYou Yu
2026-10-19 10:44 ` Jan Kara
2026-10-20 21:52   ` YouYou Yu [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=20261020215229.31406-1-youyouyu@amazon.com \
    --to=youyouyu@amazon.com \
    --cc=brauner@kernel.org \
    --cc=dgj@amazon.com \
    --cc=gunnarku@amazon.com \
    --cc=jack@suse.cz \
    --cc=lichliu@redhat.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

all inboxes | Powered by JetHome®