On Mon, Jun 17, 2019 at 6:57 PM Uladzislau Rezki <urezki@xxxxxxxxx> wrote:
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > index a9213fc3802d..5b7e50de008b 100644
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -915,7 +915,8 @@ adjust_va_to_fit_type(struct vmap_area *va,
> > {
> > struct vmap_area *lva;
> >
> > - if (type == FL_FIT_TYPE) {
> > + switch (type) {
> > + case FL_FIT_TYPE:
> > /*
> > * No need to split VA, it fully fits.
> > *
> > @@ -925,7 +926,8 @@ adjust_va_to_fit_type(struct vmap_area *va,
> > */
> > unlink_va(va, &free_vmap_area_root);
> > kmem_cache_free(vmap_area_cachep, va);
> > - } else if (type == LE_FIT_TYPE) {
> > + break;
> > + case LE_FIT_TYPE:
> > /*
> > * Split left edge of fit VA.
> > *
> > @@ -934,7 +936,8 @@ adjust_va_to_fit_type(struct vmap_area *va,
> > * |-------|-------|
> > */
> > va->va_start += size;
> > - } else if (type == RE_FIT_TYPE) {
> > + break;
> > + case RE_FIT_TYPE:
> > /*
> > * Split right edge of fit VA.
> > *
> > @@ -943,7 +946,8 @@ adjust_va_to_fit_type(struct vmap_area *va,
> > * |-------|-------|
> > */
> > va->va_end = nva_start_addr;
> > - } else if (type == NE_FIT_TYPE) {
> > + break;
> > + case NE_FIT_TYPE:
> > /*
> > * Split no edge of fit VA.
> > *
> > @@ -980,7 +984,8 @@ adjust_va_to_fit_type(struct vmap_area *va,
> > * Shrink this VA to remaining size.
> > */
> > va->va_start = nva_start_addr + size;
> > - } else {
> > + break;
> > + default:
> > return -1;
> > }
> >
> To me it is not clear how it would solve the warning. It sounds like
> your GCC after this change is able to keep track of that variable
> probably because of less generated code. But i am not sure about
> other versions. For example i have:
>
> gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
>
> and it totally OK, i.e. it does not emit any related warning.
To provide some background here, I'm doing randconfig tests, and
this warning might be one that only shows up with a specific combination
of options that add complexity to the build.
I do run into a lot -Wmaybe-uninitialized warnings, and most of the time
can figure out to change the code to be more readable by both
humans and compilers in a way that shuts up the warning. The
underlying algorithm in the compiler is NP-complete, so it can't
ever get it right 100%, but it is a valuable warning in general.
Using switch/case makes it easier for the compiler because it
seems to turn this into a single conditional instead of a set of
conditions. It also seems to be the much more common style
in the kernel.
> Another thing is that, if we add mode code there or change the function
> prototype, we might run into the same warning. Therefore i proposed that
> we just set the variable to NULL, i.e. Initialize it.
The problem with adding explicit NULL initializations is that this is
more likely to hide actual bugs if the code changes again, and the
compiler no longer notices the problem, so I try to avoid ever
initializing a variable to something that would cause a runtime
bug in place of a compile time warning later.
Arnd
