linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
	<oe-kbuild-all@lists.linux.dev>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [linux-next:master 3442/4242] WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1270 (section: __ex_table) -> .LASF0 (section: .debug_str)
Date: Wed, 10 Apr 2024 11:01:53 +0800	[thread overview]
Message-ID: <ZhYBIW8yGiqLUI8v@yujie-X299> (raw)
In-Reply-To: <ZhQcC9B3SDKyYWtl@x1n>

On Mon, Apr 08, 2024 at 12:32:11PM -0400, Peter Xu wrote:
> On Mon, Apr 08, 2024 at 12:53:19PM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   8568bb2ccc278f344e6ac44af6ed010a90aa88dc
> > commit: e79da3a55e4e7b60b2790b3402a1a6c19829e9ce [3442/4242] mm/gup: merge pXd huge mapping checks
> > config: riscv-buildonly-randconfig-r001-20230517 (https://download.01.org/0day-ci/archive/20240408/202404081248.FE1RbA1V-lkp@intel.com/config)
> > compiler: riscv32-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240408/202404081248.FE1RbA1V-lkp@intel.com/reproduce)
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202404081248.FE1RbA1V-lkp@intel.com/
> 
> [...]
> 
> > ERROR: modpost: __ex_table+0x1258 references non-executable section '.rodata.str1.4'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1260 (section: __ex_table) -> .LASF3592 (section: .debug_str)
> > ERROR: modpost: __ex_table+0x1260 references non-executable section '.debug_str'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1264 (section: __ex_table) -> .LC59 (section: .rodata.str1.4)
> > ERROR: modpost: __ex_table+0x1264 references non-executable section '.rodata.str1.4'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x126c (section: __ex_table) -> .Ldebug_ranges0 (section: .debug_ranges)
> > ERROR: modpost: __ex_table+0x126c references non-executable section '.debug_ranges'
> > >> WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1270 (section: __ex_table) -> .LASF0 (section: .debug_str)
> > ERROR: modpost: __ex_table+0x1270 references non-executable section '.debug_str'
> > >> WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1278 (section: __ex_table) -> .LASF2 (section: .debug_str)
> > ERROR: modpost: __ex_table+0x1278 references non-executable section '.debug_str'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x127c (section: __ex_table) -> .LASF0 (section: .debug_str)
> > ERROR: modpost: __ex_table+0x127c references non-executable section '.debug_str'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1284 (section: __ex_table) -> .LASF6 (section: .debug_str)
> > ERROR: modpost: __ex_table+0x1284 references non-executable section '.debug_str'
> > WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x1288 (section: __ex_table) -> .LASF7 (section: .debug_str)
> 
> [...]
> 
> Hmm, this doesn't look like relevant to the small commit e79da3a55e4e7b..
> I'd guess this is an irrelevant error with the randconfig which lacks some
> sheer luck.  I'll ignore this one as of now, but anyone can correct me
> otherwise..

Sorry for the false report. The bot wrongly parsed the modpost warnings
and triggered wrong bisections. We will fix this bug as soon as possible.

Thanks,
Yujie


      reply	other threads:[~2024-04-10  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202404081248.FE1RbA1V-lkp@intel.com>
2024-04-08 16:32 ` Peter Xu
2024-04-10  3:01   ` Yujie Liu [this message]

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=ZhYBIW8yGiqLUI8v@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=jgg@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterx@redhat.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