| 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
| ||
|
Date: Sat, 21 Mar 2015 21:29:18 +0300 From: Sergej Bauer <sergej.bauer@...il.com> To: Richard Weinberger <richard@....at> Cc: Arnd Bergmann <arnd@...db.de>, Paul Bolle <pebolle@...cali.nl>, linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org Subject: Re: [PATCH 1/1] Add mkopci driver Thanks a lot :) But the driver is really very insignificant. I was wondering about sysfs before, but consumers will not be very happy to get another revision of userspace tools/library. So this is their own problems :) Thanks again and sorry for this uselessness dialogue :) On Saturday 21 March 2015 20:32:16 Richard Weinberger wrote: > Am 21.03.2015 um 18:24 schrieb Sergej Bauer: > > Ok, I realized uselessness of merging this driver... > > Please don't give up that fast! > See: http://airlied.livejournal.com/#item80112 > > > And you brought me to a standstill: > >> passthrough. In either case, both the ioctl interface and the procfs interface have no future > > But what will be after ioctl? > > We will not drop the ioctl() system call. But having a character device with random > ioctl()s is not really a good driver design. > Today we have much more elegant ways to interact between kernel and userspace than ioctl(). > For example sysfs or netlink. > > Thanks, > //richard > -- 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/
Powered by blists - more mailing lists