From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 2/2] btrfs: verify max_inline mount parameter
Date: Tue, 13 Feb 2018 17:49:50 +0800 [thread overview]
Message-ID: <20180213094950.9412-2-anand.jain@oracle.com> (raw)
In-Reply-To: <20180213094950.9412-1-anand.jain@oracle.com>
We aren't verifying the parameter passed to the max_inline mount option,
so we won't report and fail the mount if a junk value is specified for
example, -o max_inline=abc.
This patch converts the max_inline option to %d and checks if it's a
number >= 0.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
v1->v2: use match_int ret value if error
use %u instead of %d for parser
fs/btrfs/super.c | 23 ++++++-----------------
1 file changed, 6 insertions(+), 17 deletions(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index b13d68506f15..02c7766e6849 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -344,7 +344,7 @@ static const match_table_t tokens = {
{Opt_datacow, "datacow"},
{Opt_nobarrier, "nobarrier"},
{Opt_barrier, "barrier"},
- {Opt_max_inline, "max_inline=%s"},
+ {Opt_max_inline, "max_inline=%u"},
{Opt_alloc_start, "alloc_start=%s"},
{Opt_thread_pool, "thread_pool=%d"},
{Opt_compress, "compress"},
@@ -407,7 +407,7 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,
unsigned long new_flags)
{
substring_t args[MAX_OPT_ARGS];
- char *p, *num;
+ char *p;
u64 cache_gen;
int intarg;
int ret = 0;
@@ -604,22 +604,11 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,
}
break;
case Opt_max_inline:
- num = match_strdup(&args[0]);
- if (num) {
- info->max_inline = memparse(num, NULL);
- kfree(num);
-
- if (info->max_inline) {
- info->max_inline = min_t(u32,
- info->max_inline,
- info->sectorsize);
- }
- btrfs_info(info, "max_inline at %u",
- info->max_inline);
- } else {
- ret = -ENOMEM;
+ ret = match_int(&args[0], &intarg);
+ if (ret)
goto out;
- }
+ info->max_inline = min_t(u32, intarg, info->sectorsize);
+ btrfs_info(info, "max_inline at %u", info->max_inline);
break;
case Opt_alloc_start:
btrfs_info(info,
--
2.7.0
next prev parent reply other threads:[~2018-02-13 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 9:49 [PATCH v2 1/2] btrfs: declare max_inline as u32 Anand Jain
2018-02-13 9:49 ` Anand Jain [this message]
2018-02-13 16:28 ` [PATCH v2 2/2] btrfs: verify max_inline mount parameter David Sterba
2018-02-14 17:20 ` Anand Jain
2018-02-15 16:43 ` David Sterba
2018-02-26 2:47 ` [PATCH v3] " Anand Jain
2018-02-27 15:45 ` David Sterba
2018-03-01 11:51 ` Anand Jain
2018-03-05 21:34 ` David Sterba
2018-02-13 16:28 ` [PATCH v2 1/2] btrfs: declare max_inline as u32 David Sterba
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=20180213094950.9412-2-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).