linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Yury Norov <yury.norov@gmail.com>,
	kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
	<kbuild-all@lists.01.org>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>, <linux-s390@vger.kernel.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 7287/11993] s390x-linux-ld: topology.c:undefined reference to `__tsan_memcpy'
Date: Wed, 5 Oct 2022 19:48:22 +0800	[thread overview]
Message-ID: <Yz1vBgxomxKB/Frl@rli9-MOBL1.ccr.corp.intel.com> (raw)
In-Reply-To: <YzsMHqG9LvMZXTz8@dev-arch.thelio-3990X>

On Mon, Oct 03, 2022 at 09:21:50AM -0700, Nathan Chancellor wrote:
> Hi Yury,
> 
> On Fri, Sep 30, 2022 at 06:24:47PM -0700, Yury Norov wrote:
> > On Sat, Oct 01, 2022 at 07:12:48AM +0800, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head:   274d7803837da78dfc911bcda0d593412676fc20
> > > commit: aa47a7c215e79a2ade6916f163c5a17b561bce4f [7287/11993] lib/cpumask: deprecate nr_cpumask_bits
> > > config: s390-randconfig-r023-20220926
> > > compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
> > > reproduce (this is a W=1 build):
> > >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > >         chmod +x ~/bin/make.cross
> > >         # install s390 cross compiling tool for clang build
> > >         # apt-get install binutils-s390x-linux-gnu
> > >         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=aa47a7c215e79a2ade6916f163c5a17b561bce4f
> > >         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > >         git fetch --no-tags linux-next master
> > >         git checkout aa47a7c215e79a2ade6916f163c5a17b561bce4f
> > >         # save the config file
> > >         mkdir build_dir && cp config build_dir/.config
> > >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
> > > 
> > > If you fix the issue, kindly add following tag where applicable
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > 
> > > All errors (new ones prefixed by >>):
> > > 
> > >    s390x-linux-ld: ipl.c:(.text+0x1004): undefined reference to `__tsan_memcpy'
> > >    s390x-linux-ld: ipl.c:(.text+0x1046): undefined reference to `__tsan_memset'
> > >    s390x-linux-ld: arch/s390/kernel/ipl.o: in function `reipl_fcp_scpdata_write':
> > 
> > I can't reproduce the bug. In fact, the build is broken for me on
> > next-20220930. To make the s390 image somehow building, I commented
> > out some functions that aren't found by the LD.
> 
> Sorry for the noise, this is not a kernel issue, it is a toolchain
> problem that will be fixed soon:
> 
> https://github.com/ClangBuiltLinux/linux/issues/1704
> https://lore.kernel.org/20220912094541.929856-1-elver@google.com/
> 
> I had asked the Intel folks to stop sending reports based on this build
> breakage a few times but it seems like their filter is not working
> still?

Sorry for this, we will correct the filter logic asap, it only ignores
__tsan_memset now, which should be mem* as mentioned in the link.

> 
> https://lore.kernel.org/Yx3HnuEDyFG0+G62@dev-arch.thelio-3990X/
> https://lore.kernel.org/Yy3PxL973jtEtEUK@dev-arch.thelio-3990X/
> 
> Cheers,
> Nathan
> 
> > Thanks,
> > Yury
> > 
> > diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> > index 886de028a901..d696d78132a0 100644
> > --- a/drivers/irqchip/irq-al-fic.c
> > +++ b/drivers/irqchip/irq-al-fic.c
> > @@ -235,6 +235,7 @@ static struct al_fic *al_fic_wire_init(struct device_node *node,
> >         return ERR_PTR(ret);
> >  }
> > 
> > +void __iomem *of_iomap(struct device_node *np, int index);
> >  static int __init al_fic_init_dt(struct device_node *node,
> >                                  struct device_node *parent)
> >  {
> > @@ -249,7 +250,7 @@ static int __init al_fic_init_dt(struct device_node *node,
> >                 return -EINVAL;
> >         }
> > 
> > -       base = of_iomap(node, 0);
> > +       base = NULL;//of_iomap(node, 0);
> >         if (!base) {
> >                 pr_err("%s: fail to map memory\n", node->name);
> >                 return -ENOMEM;
> > diff --git a/drivers/net/ethernet/altera/altera_tse_main.c b/drivers/net/ethernet/altera/altera_tse_main.c
> > index 7633b227b2ca..4e4c9d9743bf 100644
> > --- a/drivers/net/ethernet/altera/altera_tse_main.c
> > +++ b/drivers/net/ethernet/altera/altera_tse_main.c
> > @@ -1122,8 +1122,8 @@ static int request_and_map(struct platform_device *pdev, const char *name,
> >                 return -EBUSY;
> >         }
> > 
> > -       *ptr = devm_ioremap(device, region->start,
> > -                                   resource_size(region));
> > +       *ptr = NULL;//devm_ioremap(device, region->start,
> > +               //                  resource_size(region));
> >         if (*ptr == NULL) {
> >                 dev_err(device, "ioremap of %s failed!", name);
> >                 return -ENOMEM;
> > diff --git a/fs/afs/dir.c b/fs/afs/dir.c
> > index 230c2d19116d..9f88be3c2b08 100644
> > --- a/fs/afs/dir.c
> > +++ b/fs/afs/dir.c
> > @@ -49,6 +49,7 @@ static bool afs_dir_dirty_folio(struct address_space *mapping,
> >                 struct folio *folio)
> >  {
> >         BUG(); /* This should never happen. */
> > +       return false;
> >  }
> > 
> >  const struct file_operations afs_dir_file_operations = {
> > 
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org


      reply	other threads:[~2022-10-05 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 23:12 kernel test robot
2022-10-01  1:24 ` Yury Norov
2022-10-03 16:21   ` Nathan Chancellor
2022-10-05 11:48     ` Philip Li [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=Yz1vBgxomxKB/Frl@rli9-MOBL1.ccr.corp.intel.com \
    --to=philip.li@intel.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=yury.norov@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