lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240703155129.cbd023c14dee61e5727bb750@linux-foundation.org>
Date: Wed, 3 Jul 2024 15:51:29 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
 vincent.guittot@...aro.org, kent.overstreet@...ux.dev,
 linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH 1/1] sched.h: always_inline alloc_tag_{save|restore} to
 fix modpost warnings

On Wed,  3 Jul 2024 15:15:20 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:

> Mark alloc_tag_{save|restore} as always_inline to fix the following
> modpost warnings:
> 
> WARNING: modpost: vmlinux: section mismatch in reference: alloc_tag_save+0x1c (section: .text.unlikely) -> initcall_level_names (section: .init.data)
> WARNING: modpost: vmlinux: section mismatch in reference: alloc_tag_restore+0x3c (section: .text.unlikely) -> initcall_level_names (section: .init.data)

Well, is it only about fixing warnings?  If the warning is correct then
this might be fixing kernel crashes.

Do you know where these references are coming from?

I'm curious about the .text.unlikely.  Makes me wonder if we should
also have .init.unlikely for unlikely() calls which happen from __init
code.  Maybe we already handle that.

> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407032306.gi9nZsBi-lkp@intel.com/
> Signed-off-by: Suren Baghdasaryan <surenb@...gle.com>
> Cc: Kent Overstreet <kent.overstreet@...ux.dev>

Fixes: 22d407b164ff ("lib: add allocation tagging support for memory allocation profiling")
Cc: stable

yes?



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ