From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4527DC433E7 for ; Thu, 15 Oct 2020 03:29:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ECCDD2222E for ; Thu, 15 Oct 2020 03:29:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726832AbgJOD3c (ORCPT ); Wed, 14 Oct 2020 23:29:32 -0400 Received: from mail105.syd.optusnet.com.au ([211.29.132.249]:58375 "EHLO mail105.syd.optusnet.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726012AbgJOD3b (ORCPT ); Wed, 14 Oct 2020 23:29:31 -0400 Received: from dread.disaster.area (pa49-179-6-140.pa.nsw.optusnet.com.au [49.179.6.140]) by mail105.syd.optusnet.com.au (Postfix) with ESMTPS id 3ACD03AB414 for ; Thu, 15 Oct 2020 14:29:27 +1100 (AEDT) Received: from discord.disaster.area ([192.168.253.110]) by dread.disaster.area with esmtp (Exim 4.92.3) (envelope-from ) id 1kStxF-000eco-R5 for linux-xfs@vger.kernel.org; Thu, 15 Oct 2020 14:29:25 +1100 Received: from dave by discord.disaster.area with local (Exim 4.94) (envelope-from ) id 1kStxF-006bfk-H2 for linux-xfs@vger.kernel.org; Thu, 15 Oct 2020 14:29:25 +1100 From: Dave Chinner To: linux-xfs@vger.kernel.org Subject: [PATCH 0/5] mkfs: Configuration file defined options Date: Thu, 15 Oct 2020 14:29:20 +1100 Message-Id: <20201015032925.1574739-1-david@fromorbit.com> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.3 cv=YKPhNiOx c=1 sm=1 tr=0 cx=a_idp_d a=uDU3YIYVKEaHT0eX+MXYOQ==:117 a=uDU3YIYVKEaHT0eX+MXYOQ==:17 a=afefHYAZSVUA:10 a=SgNIeo5dlE89CoAx9fYA:9 Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org Version 2: - "-c file=xxx" > "-c options=xxx" - split out constification into new patch - removed debug output - fixed some comments - added man page stuff Hi Folks, Because needing config files for mkfs came up yet again in discussion, here is a simple implementation of INI format config files. These config files behave identically to options specified on the command line - the do not change defaults, they do not override CLI options, they are not overridden by cli options. Example: $ echo -e "[metadata]\ncrc = 0" > foo $ mkfs/mkfs.xfs -N -c options=foo -d file=1,size=100m blah Parameters parsed from config file foo successfully meta-data=blah isize=256 agcount=4, agsize=6400 blks = sectsz=512 attr=2, projid32bit=1 = crc=0 finobt=0, sparse=0, rmapbt=0 = reflink=0 data = bsize=4096 blocks=25600, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=853, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 $ And there's a V4 filesystem as specified by the option defined in the config file. If we do: $ mkfs/mkfs.xfs -N -c options=foo -m crc=1 -d file=1,size=100m blah -m crc option respecified Usage: mkfs.xfs ..... $ You can see it errors out because the CRC option was specified in both the config file and on the CLI. There's lots of stuff we can do to make the conflict and respec error messages better, but that doesn't change the basic functionality of config file based mkfs options. To allow for future changes to the way we want to apply config files, I created a full option subtype for config files. That means we can add another option to say "apply config file as default values rather than as options" if we decide that is functionality that we want to support. However, policy decisions like that are completely separate to the mechanism, so these patches don't try to address desires to ship "tuned" configs, system wide option files, shipping distro specific defaults in config files, etc. This is purely a mechanism to allow users to specify options via files instead of on the CLI. No more, no less. This has only been given a basic smoke testing right now (see above! :). I need to get Darrick's tests from the previous round of config file bikeshedding working in my test environment to do more substantial testing of this.... Cheers, Dave. Dave Chinner (5): build: add support for libinih for mkfs mkfs: add initial ini format config file parsing support mkfs: constify various strings mkfs: hook up suboption parsing to ini files mkfs: document config files in mkfs.xfs(8) configure.ac | 3 + doc/INSTALL | 5 + include/builddefs.in | 1 + include/linux.h | 2 +- m4/package_inih.m4 | 20 ++++ man/man8/mkfs.xfs.8 | 113 +++++++++++++++++++-- mkfs/Makefile | 2 +- mkfs/xfs_mkfs.c | 228 ++++++++++++++++++++++++++++++++++++++----- 8 files changed, 340 insertions(+), 34 deletions(-) create mode 100644 m4/package_inih.m4 -- 2.28.0