All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Remaining randconfig objtool warnings, linux-next-20200428
Date: Thu, 30 Apr 2020 16:05:07 +0200	[thread overview]
Message-ID: <CAK8P3a2Gzj9SVZSGo+PxWR0cMJb1sFwv+ii9J6jEGE-Z41Fr+A@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a2qLJkokMGt48JRky=WUeAbJRuNmoD1oqfWdrGSC6y1LA@mail.gmail.com>

On Tue, Apr 28, 2020 at 4:49 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> I noticed the number of objtool warnings in randconfig kernels have gone down
>  recently, maybe it's possible to eliminate the remaining ones?
>
> Here are the ones I ran into recently, using gcc-9.3:

I now cross-checked with gcc-10.0, which leads to a few additional warnings
for randconfig builds:

drivers/gpu/drm/vmwgfx/vmwgfx_msg.o: warning: objtool:
vmw_port_hb_in()+0x12f: stack state mismatch: cfa1=6+16 cfa2=7+8
drivers/gpu/drm/vmwgfx/vmwgfx_msg.o: warning: objtool:
vmw_port_hb_in()+0xca: return with modified stack frame
drivers/media/dvb-frontends/rtl2832_sdr.o: warning: objtool:
.text.unlikely: unexpected end of section
drivers/media/dvb-frontends/rtl2832_sdr.o: warning: objtool:
rtl2832_sdr_try_fmt_sdr_cap() falls through to next function
rtl2832_sdr_s_fmt_sdr_cap.cold()
kernel/kexec_core.o: warning: objtool: crash_kexec()+0x2b: unreachable
instruction
lib/locking-selftest.o: warning: objtool: locking_selftest()+0x117f:
PUSHF stack exhausted
lib/locking-selftest.o: warning: objtool: ww_tests()+0x1083: PUSHF
stack exhausted
lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x133:
call to do_strncpy_from_user() with UACCESS enabled
lib/strnlen_user.o: warning: objtool: strnlen_user()+0x122: call to
do_strnlen_user() with UACCESS enabled

I uploaded these as well now, see
https://drive.google.com/open?id=1k10cO9OkFKaMVnK7uX-prplY-13CAvW1

       Arnd

  parent reply	other threads:[~2020-04-30 14:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 14:49 Remaining randconfig objtool warnings, linux-next-20200428 Arnd Bergmann
2020-04-28 16:10 ` Josh Poimboeuf
2020-04-28 19:11   ` Kees Cook
2020-04-28 20:19   ` Arnd Bergmann
2020-04-28 20:38     ` Josh Poimboeuf
2020-04-28 21:55       ` Peter Zijlstra
2020-04-28 22:03         ` Josh Poimboeuf
2020-04-28 22:33           ` Peter Zijlstra
2020-04-28 22:48             ` Josh Poimboeuf
2020-04-28 23:08               ` Josh Poimboeuf
2020-04-29 18:55   ` Josh Poimboeuf
2020-04-29 22:46     ` Arnd Bergmann
2020-04-29 23:01       ` Josh Poimboeuf
2020-04-29 23:11       ` Josh Poimboeuf
2020-04-29 23:28         ` Josh Poimboeuf
2020-04-30 13:41           ` Arnd Bergmann
2020-04-30 14:33             ` Josh Poimboeuf
2020-04-30 19:46               ` Josh Poimboeuf
2020-04-30 20:59                 ` Arnd Bergmann
2020-04-30 21:10                   ` Josh Poimboeuf
2020-04-30 21:08                 ` Josh Poimboeuf
2020-04-30 23:02                   ` Josh Poimboeuf
2020-04-29 19:18   ` Josh Poimboeuf
2020-05-01 12:23     ` Peter Zijlstra
2020-04-30 14:05 ` Arnd Bergmann [this message]
2020-05-01  0:28   ` Josh Poimboeuf
2020-05-01 11:41     ` Arnd Bergmann
2020-05-01 17:16       ` Peter Zijlstra
2020-05-01 12:27     ` Peter Zijlstra
2020-05-01  1:07   ` Josh Poimboeuf
2020-05-01 11:18     ` Arnd Bergmann
2020-05-01 12:33     ` Peter Zijlstra
2020-05-01 13:08       ` Arnd Bergmann
2020-05-01 15:49       ` Josh Poimboeuf
2020-05-01 17:21   ` Arnd Bergmann
2020-05-01 17:26     ` Peter Zijlstra
2020-05-01 17:50       ` Josh Poimboeuf
2020-05-01 19:47         ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK8P3a2Gzj9SVZSGo+PxWR0cMJb1sFwv+ii9J6jEGE-Z41Fr+A@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.