[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201107035213.GC2499342@mit.edu>
Date: Fri, 6 Nov 2020 22:52:13 -0500
From: "Theodore Y. Ts'o" <tytso@....edu>
To: xiakaixu1987@...il.com
Cc: linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca,
Kaixu Xia <kaixuxia@...cent.com>
Subject: Re: [PATCH] ext4: report error message when setting usrjquota or
grpjquota options failed
On Thu, Oct 29, 2020 at 11:46:36PM +0800, xiakaixu1987@...il.com wrote:
> From: Kaixu Xia <kaixuxia@...cent.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@...cent.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
Powered by blists - more mailing lists