netdev - Re: [PATCH iproute2] Use PATH_MAX instead of MAXPATHLEN

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 for Android: free password hash cracker in your pocket

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

Message-ID: <55400DE7.9080501@gmail.com>
Date:	Tue, 28 Apr 2015 15:47:03 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Stephen Hemminger <stephen@...workplumber.org>,
	Felix Janda <felix.janda@...teo.de>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] Use PATH_MAX instead of MAXPATHLEN

On 27/04/15 09:13, Stephen Hemminger wrote:
> On Sat, 25 Apr 2015 22:33:28 +0200
> Felix Janda <felix.janda@...teo.de> wrote:
> 
>> They are equivalent but the former is more common. PATH_MAX is
>> specified by POSIX and needs <limits.h> while MAXPATHLEN has BSD
>> origin and needs <sys/param.h>.
>>
>> PATH_MAX has already been in use in misc/lnstat.h.
>>
>> Signed-off-by: Felix Janda <felix.janda@...teo.de>
> 
> Iproute2 is intended for use on Linux.
> It makes more sense to align with Posix than using leftover
> BSD stuff. Therefore I don't see any point in doing this.

My reading from Felix's commit message is that he is attempting to do
exactly that: conform to POSIX rather than BSD, which seems to be the
direction you are also suggesting here.
-- 
Florian
--
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