We are building the upstream kernel. There are a few patches, but nothing related to objtool. Unless you mean mainline/stable by upstream, I haven't tried that. We stick to LTS. On Thu, May 16, 2019 at 7:04 PM Josh Poimboeuf <jpoimboe@xxxxxxxxxx> wrote: > > On Thu, May 16, 2019 at 11:20:54PM +0200, Miguel Ojeda wrote: > > > mm/slub.o: warning: objtool: init_cache_random_seq()+0x36: sibling > > > call from callable instruction with modified stack frame > > > mm/slub.o: warning: objtool: slab_out_of_memory()+0x3b: sibling call > > > from callable instruction with modified stack frame > > > mm/slub.o: warning: objtool: slab_pad_check.part.0()+0x7c: sibling > > > call from callable instruction with modified stack frame > > > mm/slub.o: warning: objtool: check_slab()+0x1c: sibling call from > > > callable instruction with modified stack frame > > > > AFAIK those are non-critical, i.e. stack traces may be wrong (or not), > > but it does not mean the generated kernel itself is wrong. CC'ing the > > objtool maintainers too. > > I don't think I recognize those warnings. Do you also see them in the > upstream kernel? > > -- > Josh
