From mboxrd@z Thu Jan 1 00:00:00 1970 From: NAHieu Subject: Re: problem using xenbus interface Date: Tue, 9 Aug 2005 12:34:18 +0900 Message-ID: <5d7aca9505080820341f19352@mail.gmail.com> References: <5d7aca9505080805267dce691b@mail.gmail.com> <1123554115.13481.15.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1123554115.13481.15.camel@localhost.localdomain> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rusty Russell Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 8/9/05, Rusty Russell wrote: > On Mon, 2005-08-08 at 21:26 +0900, NAHieu wrote: > > Hello, > > > > I a writing a small kernel module for domU, in which I use xenbus and > > have some problems: > > > > I use xenbus_scanf to read value of "/restart_mode", but the below > > code always failed (got non-zero err) > > > > err =3D xenbus_scanf("/", "restart_mode", "%s", mode); >=20 > OK, if you start the xenstored with "--trace-file=3D/tmp/trace" you can > see what's happening in that file. >=20 > In this case, it's actually a bug in xenbus_scanf: it will ask to read > "//restart_mode" which is an invalid path since it has two "/" in a row. > But it's not a big problem because you shouldn't be writing in the top > level directory anyway... >=20 > I would recommend the following: >=20 > 1) Use xenbus_read here, not xenbus_scanf, since you are just reading a > single string and xenbus_read won't overflow on long strings. >=20 > 2) Use "restart-mode" not "restart_mode": we've chosen - over _ so far. >=20 Rusty, as I understand, you meant that at the moment, it is "restart-mode"? But as I checked in the latest -unstable, it is "restart_mode". So it (and others) will be converted to "restart-mode" in the future? Thank you a lot, NAH