mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: two more objtool warnings: lib/ubsan.o and fs/fs_pin.o
Date: Fri, 28 Jul 2017 12:04:47 -0500	[thread overview]
Message-ID: <20170728170447.jclf2vafqy5i2hk3@treble> (raw)
In-Reply-To: <CAK8P3a2vzKCCe7bPB0xqdzLNdDWh-7=TCiYzAYtk0KJ=oHCTAQ@mail.gmail.com>

On Fri, Jul 28, 2017 at 01:25:27PM +0200, Arnd Bergmann wrote:
> Hi Josh,
> 
> I ran into two more warnings with the two patches you sent me in private,
> using gcc-7.1.1:
> 
> lib/ubsan.o: warning: objtool: val_to_string.constprop.7()+0x97: leave
> instruction with modified stack frame
> .config: https://pastebin.com/dl/g04Dwdwx
> 
> fs/fs_pin.o: warning: objtool: pin_kill()+0x139: stack state mismatch:
> cfa1=7+88 cfa2=7+96
> .config: https://pastebin.com/dl/6gK6MadB
> 
> I assume you are faster at analysing than me, so I have not tried to get
> to the bottom of these at all. Let me know if you need help reproducing
> the warnings. It's also possible that they are fixed by some other patches
> that you already sent but that are not in linux-next yet.

Thanks.  The first one is a relatively easy fix in objtool's drap
register handling.  I have a working patch for it.

The second one is a little trickier.

Instead of:

  lea	0x8(%rsp), %rsp

GCC is doing:

  lea    0x8(%rsp), %rcx
  mov    %rcx, %rsp

I don't see why GCC would do that.  We should probably ask some GCC
folks.  Objtool isn't built to track register values, so it may be a
little tricky to deal with that pattern correctly if we can't convince
GCC to fix it.

Anyway, I'm going to be on vacation next week, but I'll investigate
further when I get back.

-- 
Josh

  reply	other threads:[~2017-07-28 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 11:25 Arnd Bergmann
2017-07-28 17:04 ` Josh Poimboeuf [this message]
2017-08-10 21:39   ` Josh Poimboeuf

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=20170728170447.jclf2vafqy5i2hk3@treble \
    --to=jpoimboe@redhat.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®