linux-kernel - config files and how to have persistent Linux kernel Driver/File System configuration info saved

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAH2r5msV1hBAGgqtMFh6P=OGPV3RKjVAER=5bg-6Y+vW5BEJwQ@mail.gmail.com>
Date:   Thu, 28 Jun 2018 17:37:15 -0500
From:   Steve French <smfrench@...il.com>
To:     linux-fsdevel <linux-fsdevel@...r.kernel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        samba-technical <samba-technical@...ts.samba.org>,
        CIFS <linux-cifs@...r.kernel.org>
Subject: config files and how to have persistent Linux kernel Driver/File
 System configuration info saved

Ronnie brought up an interesting point about the problems consistently
configuring file systems (or any Linux module for that matter) so that
reboot doesn't wipe away security or performance tuning changes.

Linux file systems typically allow configuration via various ways (I
may have left some out) for example:
- module load parameters (modprobe etc. e.g. for cachefs
"deferecreate" or "deferlookup" can be configured, as can various
parms in the nfs or cifs/smb3 modules)
- Settings via /proc/fs/ or /sys/fs (e.g. /sys/fs/ext4/features)
- Settings via mount parms

Other than /etc/fstab which is fairly limited,  AFAIK the only file
system that has persistent configuration in text files is nfs - which
allows a limited number of mount related settings to be set to
defaults via nfsmount.conf

Are there good examples of either text based configuration of Linux
kernel (preferably file system drivers) e.g. something vaguely like
/etc/btrfs or an /etc/xfs to set default security or performance
related parameters consistently over reboot of machine, or even better
something vaguely like Samba's "net conf" tools for setting
keyword=value for various types of settings in a somewhat safer way
(in a registry, which in Samba's case is cluster safe, and fairly
robust)

What is the recommended way to persist configuration settings for
Linux drivers across reboot?

-- 
Thanks,

Steve