linux-kernel - Re: [RFC][4/11][MANUX] Kernel compatibility : ioctl(2)

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

Message-ID: <534D5F11.6020108@manux.info>
Date:	Tue, 15 Apr 2014 18:32:17 +0200
From:	Emmanuel Colbus <ecolbus@...ux.info>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][4/11][MANUX] Kernel compatibility : ioctl(2)

Le 15/04/2014 18:05, One Thousand Gnomes a écrit :
>> I think this is an unproblematic extension, especially since these
>> ioctls are only supposed to be called by low-level software shipped with
>> the OS.
> 
> Thats the excuse everyone gives for messing up standards stuff. It
> usually comes back to bite you later.
> 
> If it's not ioctl don't call it ioctl, have a fdoctl() or something
> 
> Alan
> 

I see your point... Well, this looks like the most staightforward
approach then. I'll go with fdoctl().

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