From: Jan Kara <jack@suse.cz>
To: Chengguang Xu <cgxu519@mykernel.net>
Cc: Jan Kara <jack@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] quota: check quota type in early stage
Date: Tue, 8 Oct 2019 17:26:56 +0200 [thread overview]
Message-ID: <20191008152656.GA5050@quack2.suse.cz> (raw)
In-Reply-To: <20191008145059.21402-1-cgxu519@mykernel.net>
On Tue 08-10-19 22:50:59, Chengguang Xu wrote:
> Check quota type in early stage so we can avoid many
> unncessary operations when the type is wrong.
>
> Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
Yeah, checking earlier makes sense, especially since it consolidates two
checks into one. I've added your patch to my tree. Thanks!
Honza
> ---
> fs/quota/quota.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/fs/quota/quota.c b/fs/quota/quota.c
> index cb13fb76dbee..5444d3c4d93f 100644
> --- a/fs/quota/quota.c
> +++ b/fs/quota/quota.c
> @@ -60,8 +60,6 @@ static int quota_sync_all(int type)
> {
> int ret;
>
> - if (type >= MAXQUOTAS)
> - return -EINVAL;
> ret = security_quotactl(Q_SYNC, type, 0, NULL);
> if (!ret)
> iterate_supers(quota_sync_one, &type);
> @@ -686,8 +684,6 @@ static int do_quotactl(struct super_block *sb, int type, int cmd, qid_t id,
> {
> int ret;
>
> - if (type >= MAXQUOTAS)
> - return -EINVAL;
> type = array_index_nospec(type, MAXQUOTAS);
> /*
> * Quota not supported on this fs? Check this before s_quota_types
> @@ -831,6 +827,9 @@ int kernel_quotactl(unsigned int cmd, const char __user *special,
> cmds = cmd >> SUBCMDSHIFT;
> type = cmd & SUBCMDMASK;
>
> + if (type >= MAXQUOTAS)
> + return -EINVAL;
> +
> /*
> * As a special case Q_SYNC can be called without a specific device.
> * It will iterate all superblocks that have quota enabled and call
> --
> 2.21.0
>
>
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-10-08 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 14:50 Chengguang Xu
2019-10-08 15:26 ` Jan Kara [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=20191008152656.GA5050@quack2.suse.cz \
--to=jack@suse.cz \
--cc=cgxu519@mykernel.net \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
/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®