linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: xiakaixu1987@gmail.com
Cc: linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca,
	Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH] ext4: report error message when setting usrjquota or grpjquota options failed
Date: Fri, 6 Nov 2020 22:52:13 -0500	[thread overview]
Message-ID: <20201107035213.GC2499342@mit.edu> (raw)
In-Reply-To: <1603986396-28917-1-git-send-email-kaixuxia@tencent.com>

On Thu, Oct 29, 2020 at 11:46:36PM +0800, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
> 
> The macro MOPT_Q is used to indicates the mount option is quota stuff and
> would be the same as MOPT_NOSUPPORT when CONFIG_QUOTA is disabled. We want
> to report NOSUPPORT error message when setting usrjquota or grpjquota
> options with the CONFIG_QUOTA is disabled, but now it report nothing. So
> fix it by adding the MOPT_STRING flag.
> 
> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>

Thanks, applied with an improved commit description:

    The macro MOPT_Q is used to indicates the mount option is related
    to quota stuff and is defined to be MOPT_NOSUPPORT when
    CONFIG_QUOTA is disabled.  Normally the quota options are handled
    explicitly, so it didn't matter that the MOPT_STRING flag was
    missing, even though the usrjquota and grpjquota mount options
    take a string argument.  It's important that's present in the
    !CONFIG_QUOTA case, since without MOPT_STRING, the mount option
    matcher will match usrjquota= followed by an integer, and will
    otherwise skip the table entry, and so "mount option not
    supported" error message is never reported.

					- Ted

      reply	other threads:[~2020-11-07  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 15:46 [PATCH] ext4: report error message when setting usrjquota or grpjquota options failed xiakaixu1987
2020-11-07  3:52 ` Theodore Y. Ts'o [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=20201107035213.GC2499342@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=kaixuxia@tencent.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=xiakaixu1987@gmail.com \
    /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).