On Mon, Jun 13, 2016 at 02:14:39PM -0700, Andy Lutomirski wrote: > On Sun, Jun 12, 2016 at 11:57 PM, Dan Carpenter > <dan.carpenter@xxxxxxxxxx> wrote: > > It likely doesn't make a difference but my static checker complains > > that we put an upper bound on "size" but not a lower bound. Let's just > > make it unsigned. > > Shouldn't oldsize and newsize in write_ldt as well as the "size" > member in ldt_struct change, too? > Part of the joy of this check is that it complains about every time we cap the upper bound and not the lower bound so it's very thourough, but it also requires very minimal changes to silence the false positives. We know newsize can't be negative. If we change this one variable then we know oldsize and ldt_struct size can't be negative either. The problem really is that I haven't figured out out to deal with recursion... new_ldt = alloc_ldt_struct(old_mm->context.ldt->size); On the first run through, we don't know the value of ->size here so we have to assume it can be anything. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
