linux-kernel - Re: [PATCH] perf: Move fs.* to generic lib/lk/

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: <20131121150524.GA24806@ghostprotocols.net>
Date:	Thu, 21 Nov 2013 12:05:24 -0300
From:	Arnaldo Carvalho de Melo <acme@...radead.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <bp@...e.de>, Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Robert Richter <rric@...nel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/

Em Thu, Nov 21, 2013 at 01:06:05PM +0100, Borislav Petkov escreveu:
> On Thu, Nov 21, 2013 at 12:42:24PM +0100, Ingo Molnar wrote:
> > ... and just in case you are wondering why I'm making a fuss about it:
> > a naming discussion for something fundamental as this isn't bikeshed
> > painting, we really want people to look at that place to readily
> > stuff kernel related helpers into, and the name should make that very
> > obvious.
 
> No, I absolutely don't think it is a bikeshedding exercise too. We
> really need that lib because people have started growing their own
> facilities in tools/ and outside so having a lib which implements
> generic functionality for interfacing with the kernel right is going to
> save everyone a lot of time and energy.
 
> So kapi it is, I'm gonna convert what we have to it but leave time for
> acme to wake up and smell the coffee ... and the change :-)

I'm ok with having a library that has this mission statement:

"To offers various helper methods to interface with the Linux kernel:
 debugfs, procfs, sysfs handling routines with no policy, just pure,
 obvious helpers to use kernel functionality."

Naming is a bit hard, to keep it small, descriptive, as API can lead
people to think about other kinds of kernel APIs (syscalls?), "fskapi"
to mean "fs based kernel API" would perhaps be more descriptive? A
longer (more descriptive) possibility would be "linux-fskapi".

- Arnaldo

P.S.: "fskapi" also sounds, humm, fun ;-)
--
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/