From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Gergo Koteles" <soyer@irl.hu>,
"Hans de Goede" <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, "Ike Panhc" <ike.pan@canonical.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] platform/x86: ideapad-laptop: Make the scope_guard() clear of its scope
Date: Tue, 3 Sep 2024 21:52:01 -0700 [thread overview]
Message-ID: <20240904045201.v3mp4u7pcqj7qrdp@treble> (raw)
In-Reply-To: <20240829165105.1609180-1-andriy.shevchenko@linux.intel.com>
On Thu, Aug 29, 2024 at 07:50:32PM +0300, Andy Shevchenko wrote:
> First of all, it's a bit counterintuitive to have something like
>
> int err;
> ...
> scoped_guard(...)
> err = foo(...);
> if (err)
> return err;
>
> Second, with a particular kernel configuration and compiler version in
> one of such cases the objtool is not happy:
>
> ideapad-laptop.o: warning: objtool: .text.fan_mode_show: unexpected end of section
>
> I'm not an expert on all this, but the theory is that compiler and
> linker in this case can't understand that 'result' variable will be
> always initialized as long as no error has been returned. Assigning
> 'result' to a dummy value helps with this. Note, that fixing the
> scoped_guard() scope (as per above) does not make issue gone.
I'm not sure I buy that, we should look closer to understand what the
issue is. Can you share the config and/or toolchain version(s) need to
trigger the warning?
--
Josh
next prev parent reply other threads:[~2024-09-04 4:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 16:50 Andy Shevchenko
2024-09-03 15:00 ` Gergo Koteles
2024-09-03 15:14 ` Andy Shevchenko
2024-09-03 15:29 ` Gergo Koteles
2024-09-03 15:40 ` Andy Shevchenko
2024-09-04 1:22 ` Nathan Chancellor
2024-09-04 10:28 ` Andy Shevchenko
2024-09-04 13:37 ` Ilpo Järvinen
2024-09-04 4:52 ` Josh Poimboeuf [this message]
2024-09-04 10:26 ` Andy Shevchenko
2024-09-06 3:16 ` Josh Poimboeuf
2024-09-13 23:33 ` Nathan Chancellor
2024-09-16 10:40 ` Andy Shevchenko
2024-09-04 18:14 ` Hans de Goede
2024-09-04 20:18 ` Andy Shevchenko
2024-09-05 8:33 ` Hans de Goede
2024-09-05 8:36 ` Andy Shevchenko
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=20240904045201.v3mp4u7pcqj7qrdp@treble \
--to=jpoimboe@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ike.pan@canonical.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=soyer@irl.hu \
/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®