Linux-mm Archive mirror
 help / color / mirror / Atom feed
From: Alexandre Ghiti <alex@ghiti.fr>
To: kernel test robot <lkp@intel.com>, Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 10966/10967] fs/ext4/super.c:1356:(.text+0x3945c): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR15'
Date: Sat, 4 May 2024 14:48:46 +0200	[thread overview]
Message-ID: <9330574f-a06f-4a77-8cb0-3503441e0556@ghiti.fr> (raw)
In-Reply-To: <202405041522.1kGSNbp1-lkp@intel.com>

On 04/05/2024 09:57, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   9221b2819b8a4196eecf5476d66201be60fbcf29
> commit: d82ddecceb499745a8c436fb94dd0ccc0cb097b4 [10966/10967] Merge branch 'refactor-heap' of https://evilpiepirate.org/git/bcachefs.git
> config: riscv-randconfig-r005-20230228 (https://download.01.org/0day-ci/archive/20240504/202405041522.1kGSNbp1-lkp@intel.com/config)
> compiler: riscv64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240504/202405041522.1kGSNbp1-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/202405041522.1kGSNbp1-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>     riscv64-linux-ld: section .data LMA [0000000000454000,0000000001d5a5af] overlaps section .text LMA [0000000000155b70,00000000036ea517]
>     riscv64-linux-ld: section .init.pi.text VMA [ffffffff836ea518,ffffffff836ed8db] overlaps section .data VMA [ffffffff82000000,ffffffff839065af]
>     riscv64-linux-ld: section .got VMA [ffffffff839065b0,ffffffff839065bf] overlaps section .rodata VMA [ffffffff836ed900,ffffffff84390e1d]
>     riscv64-linux-ld: section .init.pi.rodata.str1.8 VMA [ffffffff84390e20,ffffffff84390ea2] overlaps section .bss VMA [ffffffff83a32000,ffffffff849e773f]
>     fs/ext4/super.o: in function `ext4_put_super':
>>> fs/ext4/super.c:1356:(.text+0x3945c): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR15'
>     fs/jffs2/malloc.o: in function `jffs2_create_slab_caches':
>>> fs/jffs2/malloc.c:36:(.init.text+0x20): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR0'
>     fs/ntfs3/frecord.o: in function `ni_new_attr_flags':
>     fs/ntfs3/frecord.c:1792:(.text+0x7ec8): relocation truncated to fit: R_RISCV_GPREL_I against symbol `ntfs_aops_cmpr' defined in .rodata section in fs/ntfs3/inode.o
>     fs/ntfs3/fslog.o: in function `is_rec_base':
>>> fs/ntfs3/ntfs.h:308:(.text+0xa774): relocation truncated to fit: R_RISCV_GPREL_I against `.L3843'
>     fs/ntfs3/inode.o: in function `put_page_testzero':
>>> include/linux/mm.h:1135:(.text+0x9fc): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR2'
>     fs/jffs2/read.o: in function `jffs2_read_dnode':
>>> fs/jffs2/read.c:41:(.text+0x200): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR0'
>     fs/jffs2/nodemgmt.o: in function `jffs2_add_physical_node_ref':
>>> fs/jffs2/nodemgmt.c:517:(.text+0x6a8): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR0'
>
> vim +1356 fs/ext4/super.c
>
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1335
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1336  	/* Debugging code just in case the in-memory inode orphan list
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1337  	 * isn't empty.  The on-disk one can be non-empty if we've
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1338  	 * detected an error and taken the fs readonly, but the
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1339  	 * in-memory list had better be clean by this point. */
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1340  	if (!list_empty(&sbi->s_orphan))
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1341  		dump_orphan_list(sb, sbi);
> 837c23fbc1b812 Chunguang Xu            2020-11-07  1342  	ASSERT(list_empty(&sbi->s_orphan));
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1343
> 89d96a6f8e6491 Theodore Ts'o           2015-06-20  1344  	sync_blockdev(sb->s_bdev);
> f98393a64ca139 Peter Zijlstra          2007-05-06  1345  	invalidate_bdev(sb->s_bdev);
> 61ead71476cf8b Christian Brauner       2024-01-23  1346  	if (sbi->s_journal_bdev_file) {
> 1489dffd51d7e4 Christoph Hellwig       2023-08-09  1347  		/*
> 1489dffd51d7e4 Christoph Hellwig       2023-08-09  1348  		 * Invalidate the journal device's buffers.  We don't want them
> 1489dffd51d7e4 Christoph Hellwig       2023-08-09  1349  		 * floating about in memory - the physical journal device may
> 1489dffd51d7e4 Christoph Hellwig       2023-08-09  1350  		 * hotswapped, and it breaks the `ro-after' testing code.
> 1489dffd51d7e4 Christoph Hellwig       2023-08-09  1351  		 */
> 61ead71476cf8b Christian Brauner       2024-01-23  1352  		sync_blockdev(file_bdev(sbi->s_journal_bdev_file));
> 61ead71476cf8b Christian Brauner       2024-01-23  1353  		invalidate_bdev(file_bdev(sbi->s_journal_bdev_file));
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1354  	}
> 50c15df69e062b Chengguang Xu           2018-12-04  1355
> dec214d00e0d78 Tahsin Erdogan          2017-06-22 @1356  	ext4_xattr_destroy_cache(sbi->s_ea_inode_cache);
> dec214d00e0d78 Tahsin Erdogan          2017-06-22  1357  	sbi->s_ea_inode_cache = NULL;
> 50c15df69e062b Chengguang Xu           2018-12-04  1358
> 47387409ee2e09 Tahsin Erdogan          2017-06-22  1359  	ext4_xattr_destroy_cache(sbi->s_ea_block_cache);
> 47387409ee2e09 Tahsin Erdogan          2017-06-22  1360  	sbi->s_ea_block_cache = NULL;
> 50c15df69e062b Chengguang Xu           2018-12-04  1361
> 618f003199c618 Pavel Skripkin          2021-04-30  1362  	ext4_stop_mmpd(sbi);
> 618f003199c618 Pavel Skripkin          2021-04-30  1363
> 9060dd2c5036b1 Eric Sandeen            2016-11-26  1364  	brelse(sbi->s_sbh);
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1365  	sb->s_fs_info = NULL;
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1366  	/*
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1367  	 * Now that we are completely done shutting down the
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1368  	 * superblock, we need to actually destroy the kobject.
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1369  	 */
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1370  	kobject_put(&sbi->s_kobj);
> 3197ebdb130473 Theodore Ts'o           2009-03-31  1371  	wait_for_completion(&sbi->s_kobj_unregister);
> 0441984a339897 Darrick J. Wong         2012-04-29  1372  	if (sbi->s_chksum_driver)
> 0441984a339897 Darrick J. Wong         2012-04-29  1373  		crypto_free_shash(sbi->s_chksum_driver);
> 705895b61133ef Pekka Enberg            2009-02-15  1374  	kfree(sbi->s_blockgroup_lock);
> 8012b866085523 Shiyang Ruan            2022-06-03  1375  	fs_put_dax(sbi->s_daxdev, NULL);
> ac4acb1f4b2b6b Eric Biggers            2020-09-16  1376  	fscrypt_free_dummy_policy(&sbi->s_dummy_enc_policy);
> 5298d4bfe80f6a Christoph Hellwig       2022-01-18  1377  #if IS_ENABLED(CONFIG_UNICODE)
> f8f4acb6cded4e Daniel Rosenberg        2020-10-28  1378  	utf8_unload(sb->s_encoding);
> c83ad55eaa91c8 Gabriel Krisman Bertazi 2019-04-25  1379  #endif
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1380  	kfree(sbi);
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1381  }
> ac27a0ec112a08 Dave Kleikamp           2006-10-11  1382
>
> :::::: The code at line 1356 was first introduced by commit
> :::::: dec214d00e0d78a08b947d7dccdfdb84407a9f4d ext4: xattr inode deduplication
>
> :::::: TO: Tahsin Erdogan <tahsin@google.com>
> :::::: CC: Theodore Ts'o <tytso@mit.edu>


And that's again a XIP kernel configuration, so nothing to worry here.

I remember we had this discussion before, but isn't there a way to 
remove the XIP config from randconfig builds?

Thanks,

Alex



      reply	other threads:[~2024-05-04 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04  7:57 [linux-next:master 10966/10967] fs/ext4/super.c:1356:(.text+0x3945c): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR15' kernel test robot
2024-05-04 12:48 ` Alexandre Ghiti [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=9330574f-a06f-4a77-8cb0-3503441e0556@ghiti.fr \
    --to=alex@ghiti.fr \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=visitorckw@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 read-only IMAP folder(s) and NNTP newsgroup(s).