linux-kernel - Re: [PATCH 2.6.21-rc1] ibmebus: Support dynamic addition and removal of adapters

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]

Date:	Tue, 20 Feb 2007 11:25:06 -0600
From:	John Rose <johnrose@...tin.ibm.com>
To:	Joachim Fenkes <FENKES@...ibm.com>
Cc:	Hoang-Nam Nguyen <hnguyen@...ux.vnet.ibm.com>,
	Me Notes <johnrose@...ibm.com>,
	lkml <linux-kernel@...r.kernel.org>,
	External List <linuxppc-dev@...abs.org>,
	Paul Mackerras <paulus@...ba.org>,
	Paul Mackerras <pmac@....ibm.com>
Subject: Re: [PATCH 2.6.21-rc1] ibmebus: Support dynamic addition
	and	removal of adapters

> If the probe operation succeeds, the respective device will show up 
> beneath
> /sys/bus/ibmebus/devices.

This approach is not particularly synchronous.  Take the case of an add
failure: how long would an application wait before deciding that the new
device is not going to appear?

It might be preferable to have the write to the probe function fail. 
For example, if we can't find the device node, return -EINVAL or
something.

> This is already taken care of by of_device_register().

If we are scrapping the use of of_device for ibmebus devices, can we
still create a devspec file for OF correlation purposes?

Thanks-
John

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