linux-kernel - Re: Class device namespaces

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: <20090427172710.5a0c7f48@hyperion.delvare>
Date:	Mon, 27 Apr 2009 17:27:10 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Michael E Brown <mebrown@...haels-house.net>
Cc:	Kay Sievers <kay.sievers@...y.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Matt Domsch <Matt_Domsch@...l.com>
Subject: Re: Class device namespaces

Hi Michael,

On Mon, 27 Apr 2009 08:20:43 -0500, Michael E Brown wrote:
> On Sun, Apr 26, 2009 at 08:54:01AM +0200, Jean Delvare wrote:
> > Hi Kay,
> > 
> > Sorry, completely overlooked your reply... Ah, now I remember, I was
> > waiting for Michael to show up and comment on this. Michael, ping? As
> > long as we don't know the exact requirements and constraints of the
> > dell firmware tool, we're somewhat stuck.
> > 
> > Matt, maybe you can help? Could you please point us to the source code
> > of the dell firmware tool which relies on the dell_rbu driver?
> 
> Sorry about that. Skimmed the thread and looks like I missed out...
> 
> The problem is that there are two users: 1) libsmbios as Matt has
> already mentioned, and 2) Dell OpenMange Server Administrator.
> Specifically srvadmin-hapi has the code to use the dell_rbu code
> (proprietary, no source available). The srvadmin-hapi code is embedded
> into all Dell Update Packages (DUPs).
> 
> The problem being that any change to the paths breaks all released DUPs.

The question was: any change to _which_ paths exactly? Sysfs often
offers several ways to reach the same object, and it matters to know
which need to be preserved and which can change.

Looking at src/libsmbios_c++/rbu/Rbu_Linux.cpp, I see the following
paths are used:

const char *rbu_v1_mono_data_file = "/sys/firmware/rbu/rbudata";
const char *rbu_v1_mono_size_file = "/sys/firmware/rbu/rbudatasize";
const char *rbu_v1_pkt_data_file = "/sys/firmware/rbu/packetdata";
const char *rbu_v1_pkt_size_file = "/sys/firmware/rbu/packetdatasize";

const char *rbu_v2_fw_data_file = "/sys/class/firmware/dell_rbu/data";
const char *rbu_v2_fw_load_file = "/sys/class/firmware/dell_rbu/loading";
const char *rbu_v2_img_type_file = "/sys/devices/platform/dell_rbu/image_type";
const char *rbu_v2_pkt_size_file = "/sys/devices/platform/dell_rbu/packet_size";

I guess that noawadays v2 applies, so the only path which needs to be
preserved is "/sys/class/firmware/dell_rbu". Is that correct? Is it the
same for srvadmin-hap?

Thanks,
-- 
Jean Delvare
--
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/