diff options
| author |   Kaixu Xia <kaixuxia@tencent.com> | 2020-10-29 23:46:36 +0800 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2020-11-06 22:52:35 -0500 |
| commit | 174fe5ba2d1ea0d6c5ab2a7d4aa058d6d497ae4d (patch) | |
| tree | d2e7ae81d2e99c7b08142d9a59629424139dbc6b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Linux 5.10-rc2 (diff) | |
| download | wireguard-linux-174fe5ba2d1ea0d6c5ab2a7d4aa058d6d497ae4d.tar.xz wireguard-linux-174fe5ba2d1ea0d6c5ab2a7d4aa058d6d497ae4d.zip | |
ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA
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.
[ Fixed up the commit description to better explain why the fix
works. --TYT ]
Fixes: 26092bf52478 ("ext4: use a table-driven handler for mount options")
Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>
Link: https://lore.kernel.org/r/1603986396-28917-1-git-send-email-kaixuxia@tencent.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions