| 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
| ||
|
Message-ID: <22778.1204735199@vena.lwn.net> Date: Wed, 05 Mar 2008 09:39:59 -0700 From: corbet@....net (Jonathan Corbet) To: device-mapper development <dm-devel@...hat.com> Cc: Daniel Phillips <phillips@...nq.net>, linux-kernel@...r.kernel.org Subject: Re: [RFC] An alternative interface to device mapper Hey, Daniel, > In more detail: ddlink is a generic pipe-like interface for controlling > device drivers. I'm not in a position to say much about the wider picture at the moment, but one quibble comes immediately to mind: why do you create yet another communication path into the kernel rather than using netlink, which is already there and used in a number of other contexts? jon -- 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