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: <20090321.132239.74116822.davem@davemloft.net>
Date:	Sat, 21 Mar 2009 13:22:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dwmw2@...radead.org
Cc:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: [PATCH 06/30] solos: Handle attribute show/store in kernel
 more sanely

From: David Woodhouse <dwmw2@...radead.org>
Date: Tue, 17 Mar 2009 22:49:32 +0000

> On Tue, 2009-03-17 at 15:44 -0700, Stephen Hemminger wrote:
> > Since these are generic, please use some form of netlink for this
> > instead of sysfs.
> > 
> > Bonding was the first mistake (trying to use sysfs for a transactional
> > API).
> > Pls don't repeat the mistake.
> 
> It's not a transactional API.
> 
> The sysfs model actually fits the communication with the hardware almost
> perfectly -- there are a bunch of named parameters, all of which can be
> read and a few of which can be written to. A sysfs read or write
> translates directly into a single exchange with the device's firmware.

Fair enough, I'll pull this into net-next-2.6
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ