Re: [libvirt] [PATCH] Make really sure we don't access non-existing vCPUs

On Tue, Jul 12, 2016 at 17:54:03 +0200, Martin Kletzander wrote: > On Tue, Jul 12, 2016 at 03:01:57PM +0200, Peter Krempa wrote: > >On Tue, Jul 12, 2016 at 13:44:10 +0200, Martin Kletzander wrote: [...] > >> I could've pushed this as a build breaker, but I'm not really sure > >> everyone will like this to be handled this way. I also did another > >> fix for this where we don't do int->size_t->int casting all the time, > >> but it's probably not worth the hassle. Also I don't know whether > >> Peter has more stuff for this in his pockets now, so I figured I > >> rather submit this for review. > > > >It's impossible since virDomainDefGetVcpu returns a valid pointer if i > >is less than def->maxvcpus. > > > > It is, but only thanks to how we work with the structure. Since > def->vcpus is not virDomainVcpuDefPtr but rather _array_ of > virDomainVcpuDefPtr, then it *can* be NULL very easily. I know we don't It can't. Just the compiler thinks it can. We allocate it densely. > deal with checking member[x] when x < nmembers, but OTOH it's not that > often array of pointers. Also we do this very similar thing somewhere > else, and the compiler doesn't complain, so we can change to that or > just leave it as it is. > > Just so you know, my reasoning for this was that sparse vcpus could > cause the array to be not mapped fully. I see now that every one of > those pointers are mapped even when it's not needed, so I guess that's > invalid. No idea why we have that as an array of pointers then. Since I've added private data every single member of the array needs to be initialized separately. I've opted for allocating them separately to go with the majority of our functions. I still plan for that to remain densely allocated. > >Since we are rather adding dead code than not supporting broken > >toolchain ... ACK. > > > > The toolchain is actually not broken. The assumption from the syntactic > POV is valid. If we thought it is broken we'd probably use > -Wno-null-dereference or similar. We've already added some dead code because of that check. > If two lines of dead code (that are clearly readable) are that annoying It might hint to readers that the array is indeed sparse. Reading the code again I now think that rather than skipping the loop the check for vcpu should be moved into the if right below it: if (vcpu && vcpu->cpumask) bitmap = vcpu->cpumask; By skipping the loop you don't fill anything which is semanticaly wrong in context of that function. > to you (more than size_t->int->size_t hindering readability in that Erm, yes, that was bugging me and I'm not sure why I didn't get rid of that when I was refactoring it. > function), I suggest raising that concern in a separate discussion on > the ML so that we have a consensus about dealing with MinGW, clang, > coverity, gcc > 4.9 and other scenarios that cause this. Way less > people will read it when it's just part of a review for three-line > build-breaker (from my experience). > > I, for one, don't really care about this that much, so I won't push > this. Let's see how we resolve this once and for all (unless someone > pushes another patch under the build-breaker rule). Or you could push this righ away since I clearly ACKed it.