linux-kernel - Re: [PATCH 001/001] CHAR DRIVERS: a simple device to give daemons a /sys-like interface

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5206B994.9050603@linuxtoys.org>
Date:	Sat, 10 Aug 2013 15:07:16 -0700
From:	Bob Smith <bsmith@...uxtoys.org>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 001/001] CHAR DRIVERS: a simple device to give daemons
 a /sys-like interface

Arnd Bergmann wrote:
>> GOAL
>> The goal of this patch was to make it possible to configure
>> daemons using simple file IO.  The litmus test for this is
>> that commands like these should be possible
>>          cat < /var/daemons/wpa_supplicant/use_channel
>>          echo 5 >/var/daemons/wpa_supplicant/use_channel

> If you want to have that behavior, I think the best way to
> do it would be new file system that combines aspects of
> tmpfs and debugfs, letting users with write access to the
> mount point (or a directory under it) create subdirectories
> and files using regular unix permission handling. You would
> then always use the file_operations that you defined for your
> chardev but use that with inode_operations similar to tmpfs.

THANKS!  It would still be a kernel patch and still require
root to set up but so would FUSE and your approach might be
much lighter weight.

thanks
Bob Smith



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/