netdev - Re: [PATCH 02/39] wimax: declarations for the in-kernel WiMAX API

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]

Date:	Tue, 2 Dec 2008 18:07:31 -0800
From:	Inaky Perez-Gonzalez <inaky@...ux.intel.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 02/39] wimax: declarations for the in-kernel WiMAX API

On Thursday 27 November 2008, Johannes Berg wrote:
> Why bother versioning the API? Since this is generic netlink, and things
> are looked up by the family name, a completely new version would just
> use a new family name and be done with it, old userspace won't even
> _find_ that new "version" of the API.

That'd be a way to do majors -- hadn't thought about it.

But then, it forces a way to create "a way to grok versions" in the
family name, which is moving the problem from one place to the other.

Because parsing in the family means having to set a protocol and
parsing ASCII, I'd say it's easier to use the family's version field,
as it is available.

> The "minor version" seems also
> useless, either you can do the change in a backward compatible way or
> you cannot and need to provide compat code.

No it is not -- you are missing the case of adding an API
call/signal. Addition doesn't break backwards compatibility, yet a
user that requires the addition has to double check it is
available.

-- 
Inaky

--
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