From: Vladimir Panteleev <git@thecybershadow.net>
To: linux-btrfs@vger.kernel.org
Cc: Vladimir Panteleev <git@thecybershadow.net>
Subject: [PATCH 0/1] btrfs: Simplify parsing max_inline mount option
Date: Thu, 15 Aug 2019 02:04:52 +0000 [thread overview]
Message-ID: <20190815020453.25150-1-git@thecybershadow.net> (raw)
A nit I noticed when writing the global_reserve_size patch.
I'm assuming that rejecting garbage in mount options (where it was
silently accepted before) does not break the first rule of kernel
development?
Vladimir Panteleev (1):
btrfs: Simplify parsing max_inline mount option
fs/btrfs/super.c | 24 +++++++++---------------
1 file changed, 9 insertions(+), 15 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-15 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 2:04 Vladimir Panteleev [this message]
2019-08-15 2:04 ` [PATCH 1/1] btrfs: Simplify parsing max_inline mount option Vladimir Panteleev
2019-08-15 4:54 ` Anand Jain
2019-08-15 14:54 ` Vladimir Panteleev
2019-08-21 14:35 ` David Sterba
2019-08-21 15:16 ` Vladimir Panteleev
2019-08-21 16:08 ` 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=20190815020453.25150-1-git@thecybershadow.net \
--to=git@thecybershadow.net \
--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).