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: <20090428101020.0e4c2b0c@hyperion.delvare>
Date:	Tue, 28 Apr 2009 10:10:20 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Michael 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>,
	Douglas Warzecha <Douglas_Warzecha@...l.com>
Subject: Re: Class device namespaces

On Mon, 27 Apr 2009 12:23:30 -0500, Michael Brown wrote:
> On Mon, Apr 27, 2009 at 10:27 AM, Jean Delvare <khali@...ux-fr.org> wrote:
> > 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.
> >
> > 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?
> 
> You are correct WRT libsmbios. For hapi, I've cc'd Doug who can tell
> you about their code. I've done a quick grep of their code, and the
> paths above look like the same ones he is using, but I could be wrong.
> 
> hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> HBAS_RBU_SYSFS_NEW_DATAREAD_PFNAME		"/sys/devices/platform/dell_rbu/data"
> hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> HBAS_RBU_SYSFS_NEW_IMAGETYPE_PFNAME		"/sys/devices/platform/dell_rbu/image_type"
> hapi/apilibrary/dchbas/linux/umhbaslx.c:#define
> HBAS_RBU_SYSFS_NEW_PKTSIZE_PFNAME		"/sys/devices/platform/dell_rbu/packet_size"

This doesn't make use of the firmware class at all, so I guess it won't
be affected by any change to the firmware class?

-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ