From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5559978816317563590==" MIME-Version: 1.0 From: John Ogness To: kbuild-all@lists.01.org Subject: Re: [linux-next:master 6188/10009] h8300-linux-ld: section .softirqentry.text VMA overlaps section .bss VMA Date: Mon, 27 Jul 2020 14:00:00 +0206 Message-ID: <87365d5g2v.fsf@jogness.linutronix.de> In-Reply-To: <202007222325.dWX4OQX0%lkp@intel.com> List-Id: --===============5559978816317563590== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 2020-07-22, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.g= it master > head: de2e69cfe54a8f2ed4b75f09d3110c514f45d38e > commit: 896fbe20b4e2333fb55cc9b9b783ebcc49eee7c7 [6188/10009] printk: use= the lockless ringbuffer > config: h8300-randconfig-c022-20200720 (attached as .config) > compiler: h8300-linux-gcc (GCC) 9.3.0 > reproduce (this is a W=3D1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbi= n/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > git checkout 896fbe20b4e2333fb55cc9b9b783ebcc49eee7c7 > # save the attached .config to linux build tree > COMPILER_INSTALL_PATH=3D$HOME/0day COMPILER=3Dgcc-9.3.0 make.cros= s ARCH=3Dh8300 = > > If you fix the issue, kindly add following tag as appropriate > Reported-by: kernel test robot > > All errors (new ones prefixed by >>): > > h8300-linux-ld: section .init.text LMA [00000000005eaf40,0000000000621= 00b] overlaps section .text LMA [000000000000025c,00000000007942cf] > h8300-linux-ld: section .data VMA [0000000000400000,00000000005eaf3f] = overlaps section .text VMA [000000000000025c,00000000007942cf] >>> h8300-linux-ld: section .softirqentry.text VMA [00000000007942d0,000000= 0000794597] overlaps section .bss VMA [000000000062c340,0000000000847b4f] The .bss section for the h8300 is relatively small. A default CONFIG_LOG_BUF_SHIFT value of 20 will create a static printk ringbuffer that is too large. This is a problem with the new printk ringbuffer because it now occupies double the .bss space. Is it enough to ignore this problem and require h8300 users to use a smaller CONFIG_LOG_BUF_SHIFT value (which they probably are anyway)? Or should we change the default for CONFIG_H8300? I am open for ideas. John Ogness --===============5559978816317563590==--