From: Nick Desaulniers <ndesaulniers@google.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 209/215] mm/mmap.c:2430:29: error: assigning to 'lockdep_map_p' from incompatible type 'void *'
Date: Tue, 18 Jul 2023 10:14:47 -0700 [thread overview]
Message-ID: <CAKwvOdn1Uc-xZk81Adooq0tVHo6M9Jn6=OXhiJs07X3nrJst+Q@mail.gmail.com> (raw)
In-Reply-To: <20230718171025.vn67ydtjifawkvqo@revolver>
On Tue, Jul 18, 2023 at 10:10 AM Liam R. Howlett
<Liam.Howlett@oracle.com> wrote:
>
> * kernel test robot <lkp@intel.com> [230717 19:36]:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> > head: 75ac3c8cee9c94691bc9001fcfb6214ae812bfa8
> > commit: f40b24c7c416b304b93115d66d02dc54e5d2f7d1 [209/215] mm/mmap: change detached vma locking scheme
> > config: um-allnoconfig (https://download.01.org/0day-ci/archive/20230718/202307180750.Dk6xL6nG-lkp@intel.com/config)
> > compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
>
> Just a status update on this..
>
> The above config works with clang 16, I will reproduce it with the
> periodic build of clang 17 once I locate a copy.
>
> The llvm repositories currently don't have 17 [1], so this is delaying
> the reproducibility and fix for the issue.
They do, see the second hit for `development branch` on that page.
Thanks for testing!
>
> [1] https://apt.llvm.org/
>
> Thanks,
> Liam
>
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2023-07-18 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 23:35 kernel test robot
2023-07-18 17:10 ` Liam R. Howlett
2023-07-18 17:14 ` Nick Desaulniers [this message]
2023-07-18 17:21 ` Nathan Chancellor
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='CAKwvOdn1Uc-xZk81Adooq0tVHo6M9Jn6=OXhiJs07X3nrJst+Q@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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