[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1527480795.2693.4.camel@themaw.net>
Date: Mon, 28 May 2018 12:13:15 +0800
From: Ian Kent <raven@...maw.net>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Paul Menzel <pmenzel+linux-kasan-dev@...gen.mpg.de>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>, kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix
On Fri, 2018-05-25 at 20:48 -0700, Andrew Morton wrote:
> On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot <lkp@...el.com> wrote:
>
> > Hi Andrey,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on mmotm/master]
> > [cannot apply to v4.17-rc6]
> > [if your patch is applied to the wrong git tree, please drop us a note to
> > help improve the system]
> >
> > url: https://github.com/0day-ci/linux/commits/Andrey-Ryabinin/mm-kasan-do
> > nt-vfree-nonexistent-vm_area-fix/20180526-093255
> > base: git://git.cmpxchg.org/linux-mmotm.git master
> > config: sparc-allyesconfig (attached as .config)
> > compiler: sparc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/m
> > ake.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > make.cross ARCH=sparc
> >
> > All errors (new ones prefixed by >>):
> >
> > fs/autofs/inode.o: In function `autofs_new_ino':
> > inode.c:(.text+0x220): multiple definition of `autofs_new_ino'
> > fs/autofs/inode.o:inode.c:(.text+0x220): first defined here
> > fs/autofs/inode.o: In function `autofs_clean_ino':
> > inode.c:(.text+0x280): multiple definition of `autofs_clean_ino'
> > fs/autofs/inode.o:inode.c:(.text+0x280): first defined here
>
> There's bot breakage here - clearly that patch didn't cause this error.
>
> Ian, this autofs glitch may still not be fixed.
Yes, autofs-make-autofs4-Kconfig-depend-on-AUTOFS_FS.patch should have
fixed that.
I tied a bunch of .config combinations and I was unable to find any that
lead to both CONFIG_AUTOFS_FS and CONFIG_AUTOFS4_FS being defined.
I must be missing something else, I'll investigate.
Ian
Powered by blists - more mailing lists