On Thu, Mar 17, 2011 at 03:36:08PM +1030, Rusty Russell wrote: > > I'm happ to switch strcmp. > > Of course, that's assuming buf is nul terminated.
It's the string the user writes into it, which normally should be nul-terminated. > > No, it's intentional. config space writes can't return errors, so we need > > to check that the value has really changed. I'll add a comment explaining > > it. > > OK, under what circumstances could it fail? > > If you're using this mechanism to indicate that the host doesn't support > the feature, that's making an assumption about the nature of config > space writes which isn't true for non-PCI virtio. > > ie. lguest and S/390 don't trap writes to config space. > > Or perhaps they should? But we should be explicit about needing it... We have the features flag to indicate if updating the caching mode is supported, but we we could still fail it for other reasons - e.g. we could fail to reopen the file with/without O_SYNC. But if lguest or S/390 don't support trapping config space write this feature won't work for them at all. As do other features that make use of config space write, e.g. updating the MAC address for virtio-net.
