linux-kernel - Re: Rules on how to use sysfs in userspace programs

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

Message-ID: <466A9DDD.2040107@ums.usu.ru>
Date:	Sat, 09 Jun 2007 18:32:29 +0600
From:	"Alexander E. Patrakov" <patrakov@....usu.ru>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>, daniel.ritz@....ch,
	linux@...do.de
Subject: Re: Rules on how to use sysfs in userspace programs

Greg KH wrote:
> - Do not use libsysfs
>   It makes assumptions about sysfs which are not true. Its API does not
>   offer any abstraction, it exposes all the kernel driver-core
>   implementation details in its own API. Therefore it is not better than
>   reading directories and opening the files yourself.
>   Also, it is not actively maintained, in the sense of reflecting the
>   current kernel-development. The goal of providing a stable interface
>   to sysfs has failed, it causes more problems, than it solves. It
>   violates many of the rules in this document.

The problem is that even on ftp.kernel.org there are packages like 
pcmciautils that still link to libsysfs and contain things like #define 
PATH_TO_SOCKET "/sys/class/pcmcia_socket/". Are they expected to be fixed?

-- 
Alexander E. Patrakov
-
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/