From: Daniel Gomez <da.gomez@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>
Cc: "Kees Cook" <kees@kernel.org>,
"Joel Granados" <joel.granados@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: linux-next: manual merge of the sysctl tree with the modules tree
Date: Thu, 31 Jul 2025 14:05:23 +0200 [thread overview]
Message-ID: <2f54da1b-0670-4f6f-b170-228ff90e624e@samsung.com> (raw)
In-Reply-To: <20250731110249.646be7ac@canb.auug.org.au>
On 7/31/2025 3:02 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 14 Jul 2025 17:59:16 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Today's linux-next merge of the sysctl tree got a conflict in:
>>
>> include/linux/module.h
>>
>> between commits:
>>
>> 6633d3a45a8c ("module: move 'struct module_use' to internal.h")
>> a55842991352 ("module: make structure definitions always visible")
>>
>> from the modules tree and commit:
>>
>> 6bb37af62634 ("module: Move modprobe_path and modules_disabled ctl_tables into the module subsys")
>>
>> from the sysctl tree.
>>
>> I fixed it up (see below) and can carry the fix as necessary. This
>> is now fixed as far as linux-next is concerned, but any non trivial
>> conflicts should be mentioned to your upstream maintainer when your tree
>> is submitted for merging. You may also want to consider cooperating
>> with the maintainer of the conflicting tree to minimise any particularly
>> complex conflicts.
>>
>>
>> diff --cc include/linux/module.h
>> index 3b665cb0cabe,e93cdb92ad92..000000000000
>> --- a/include/linux/module.h
>> +++ b/include/linux/module.h
>> @@@ -584,17 -608,6 +584,16 @@@ struct module
>> #define MODULE_ARCH_INIT {}
>> #endif
>>
>> +#ifdef CONFIG_MODULES
>> +
>> - extern int modules_disabled; /* for sysctl */
>> +/* Get/put a kernel symbol (calls must be symmetric) */
>> +void *__symbol_get(const char *symbol);
>> +void *__symbol_get_gpl(const char *symbol);
>> +#define symbol_get(x) ({ \
>> + static const char __notrim[] \
>> + __used __section(".no_trim_symbol") = __stringify(x); \
>> + (typeof(&x))(__symbol_get(__stringify(x))); })
>> +
>> #ifndef HAVE_ARCH_KALLSYMS_SYMBOL_VALUE
>> static inline unsigned long kallsyms_symbol_value(const Elf_Sym *sym)
>> {
>
> This is now a conflict between the modules tree and Linus' tree.
Thanks for the heads-up.
modules tree is now rebased on top of Linus's tree with the conflict
solved.
next prev parent reply other threads:[~2025-07-31 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 7:59 linux-next: manual merge of the sysctl tree with the modules tree Stephen Rothwell
2025-07-21 10:49 ` Joel Granados
2025-07-31 1:02 ` Stephen Rothwell
2025-07-31 12:05 ` Daniel Gomez [this message]
2025-08-04 7:49 ` Joel Granados
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=2f54da1b-0670-4f6f-b170-228ff90e624e@samsung.com \
--to=da.gomez@samsung.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.weissschuh@linutronix.de \
/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