From: Adam Borowski <kilobyte@angband.pl>
To: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v3 0/1] asm prototypes for modversions on x86
Date: Sun, 11 Dec 2016 01:52:11 +0100 [thread overview]
Message-ID: <20161211005211.GA11607@angband.pl> (raw)
Hi!
After Linus' revert of Arnd's modversions patch, it looks like we're back to
wanting asm-prototypes.h at least in the short term. Things are much better
than before -- instead of failing to load modules there's just a scary
warning, but I still believe that no scary warning is better :)
Users will be stressed, waste their time looking for answer, etc -- and the
short-term fix is quite well researched and tested. It's for x86 only, but
with arm ppc arm64 already dealt with, that handles about 99.9% of machines.
So I think it'd be good if you could apply this -- ideally for 4.9, if not
then at least 4.10.
There _is_ a modification since the last posted version: Ben Hutchings
pointed out that I missed one 486-only symbol. Not surprising no one found
this during testing...
The diff from v2 is:
+#ifndef CONFIG_X86_CMPXCHG64
+extern void cmpxchg8b_emu(void);
+#endif
Note that this is already carried by Debian (Ben Hutchings' tree), so a
mainline fix for 4.9 would matter only for other distributions, not sure
which if any want to release with 4.9.
Meow!
--
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination. You need a black-handled knife, and
an appropriate set of candles (number and color matters). Or was it a
silver-handled knife? Crap, need to look that up.
next reply other threads:[~2016-12-11 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 0:52 Adam Borowski [this message]
2016-12-11 1:09 ` [PATCH v3 1/1] x86/kbuild: enable modversions for symbols exported from asm Adam Borowski
2016-12-13 23:39 ` Michal Marek
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=20161211005211.GA11607@angband.pl \
--to=kilobyte@angband.pl \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).