From: Randy Dunlap <rdunlap@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>
Subject: Re: linux-next 20190611: objtool warning
Date: Tue, 11 Jun 2019 20:17:20 -0700 [thread overview]
Message-ID: <18e6ef70-2fa3-3f70-0fcd-3eadef2cfceb@infradead.org> (raw)
In-Reply-To: <20190612025227.lxumqqtqao6iqms3@treble>
On 6/11/19 7:52 PM, Josh Poimboeuf wrote:
> On Tue, Jun 11, 2019 at 06:59:22PM -0700, Randy Dunlap wrote:
>> Hi,
>>
>> New warning AFAIK:
>>
>> drivers/hwmon/smsc47m1.o: warning: objtool: fan_div_store()+0x11f: sibling call from callable instruction with modified stack frame
>
> I'm getting a different warning:
>
> drivers/hwmon/smsc47m1.o: warning: objtool: fan_div_store()+0xb6: can't find jump dest instruction at .text+0x93a
>
> But I bet the root cause is the same.
>
> This fixes it for me:
>
> From: Josh Poimboeuf <jpoimboe@redhat.com>
> Subject: [PATCH] hwmon/smsc47m1: Fix objtool warning caused by undefined behavior
>
> Objtool is reporting the following warning:
>
> drivers/hwmon/smsc47m1.o: warning: objtool: fan_div_store()+0xb6: can't find jump dest instruction at .text+0x93a
>
> It's apparently caused by
>
> 2cf6745e69d1 ("hwmon: (smsc47m1) fix (suspicious) outside array bounds warnings")
>
> which is somehow convincing GCC to add a jump past the end of the
> function:
>
> 793: 45 85 ed test %r13d,%r13d
> 796: 0f 88 9e 01 00 00 js 93a <fan_div_store+0x25a>
> ...
> 930: e9 5e fe ff ff jmpq 793 <fan_div_store+0xb3>
> 935: e8 00 00 00 00 callq 93a <fan_div_store+0x25a>
> 936: R_X86_64_PLT32 __stack_chk_fail-0x4
> <function end>
>
> I suppose this falls under the category of undefined behavior, so we
> probably can't call it a GCC bug. But if the value of "nr" were out of
> range somehow then it would start executing random code. Use a runtime
> BUG() assertion to avoid undefined behavior.
>
> Fixes: 2cf6745e69d1 ("hwmon: (smsc47m1) fix (suspicious) outside array bounds warnings")
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Yes, that works for me. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/hwmon/smsc47m1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/smsc47m1.c b/drivers/hwmon/smsc47m1.c
> index 6d366c9cb906..b637836b58a1 100644
> --- a/drivers/hwmon/smsc47m1.c
> +++ b/drivers/hwmon/smsc47m1.c
> @@ -352,7 +352,7 @@ static ssize_t fan_div_store(struct device *dev,
> smsc47m1_write_value(data, SMSC47M2_REG_FANDIV3, tmp);
> break;
> default:
> - unreachable();
> + BUG();
> }
>
> /* Preserve fan min */
>
--
~Randy
next prev parent reply other threads:[~2019-06-12 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 1:59 Randy Dunlap
2019-06-12 2:52 ` Josh Poimboeuf
2019-06-12 3:17 ` Randy Dunlap [this message]
2019-06-12 5:09 ` Guenter Roeck
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=18e6ef70-2fa3-3f70-0fcd-3eadef2cfceb@infradead.org \
--to=rdunlap@infradead.org \
--cc=jdelvare@suse.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peterz@infradead.org \
--cc=yamada.masahiro@socionext.com \
/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®