[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121119.144745.1093556126398582629.davem@davemloft.net>
Date: Mon, 19 Nov 2012 14:47:45 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: sven@...fation.org
Cc: b.a.t.m.a.n@...ts.open-mesh.org, bhutchings@...arflare.com,
ordex@...istici.org, netdev@...r.kernel.org, lindner_marek@...oo.de
Subject: Re: [B.A.T.M.A.N.] [PATCH 04/10] batman-adv: export compatibility
version via debugfs
From: Sven Eckelmann <sven@...fation.org>
Date: Mon, 19 Nov 2012 20:29:07 +0100
> On Monday 19 November 2012 18:52:30 Ben Hutchings wrote:
>> On Mon, 2012-11-19 at 09:24 +0100, Antonio Quartulli wrote:
>> > Different versions of the batman-adv module may use the same compatibility
>> > version, but this is not understandable at runtime (the only way is to
>> > parse the kernel log and fetch the batman-adv advertisement message on
>> > loading). The user may want to know whether two nodes using different
>> > versions can communicate or not. For this purpose the module has to
>> > export this value through debugfs.
>> [...]
>>
>> I do hope that you're not planning to use unstable debugfs interfaces
>> indefinitely.
>
> Why are you refering to the adding of an file as "incompatible" debugfs
> interface? I would call it additional information. And the rest of the commit
> message is talking about *possible* protocol incompatibilies of the network
> protocol (which caused this uncontrolled erruption of anger in a network
> maintainer).
Debugfs files aren't where you store information that userspace actually
uses in normal situations.
It's for developer debug, to expose internals that otherwise have no
business being part of the user visible interfaces.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists