From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Zi Yan <ziy@nvidia.com>, Johannes Weiner <hannes@cmpxchg.org>,
kernel test robot <lkp@intel.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
David Hildenbrand <david@redhat.com>,
Eric Ren <renzhengeek@gmail.com>,
Mel Gorman <mgorman@techsingularity.net>,
Mike Rapoport <rppt@linux.ibm.com>,
Minchan Kim <minchan@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Vlastimil Babka <vbabka@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [mm] 23e12fc477: UBSAN:shift-out-of-bounds_in_mm/page_isolation.c
Date: Tue, 10 May 2022 14:19:04 -0700 [thread overview]
Message-ID: <20220510141904.242d9301d109d413ea10e978@linux-foundation.org> (raw)
In-Reply-To: <20220510095824.GB3969@xsang-OptiPlex-9020>
On Tue, 10 May 2022 17:58:24 +0800 kernel test robot <oliver.sang@intel.com> wrote:
> commit: 23e12fc477f1c2729af51c427087e777d6e63803 ("mm: make alloc_contig_range work at pageblock granularity")
> https://github.com/hnaz/linux-mm master
That tree is no longer being updated. Please switch to
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Either the mm-unstable branch (hotfixes and MM) or the mm-everything
branch (mm-unstable plus non-MM patches).
mm-unstable includes
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-make-alloc_contig_range-work-at-pageblock-granularity-fix.patch,
which quite possibly fixes the issue you have detected.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: lkp@lists.01.org
Subject: Re: [mm] 23e12fc477: UBSAN:shift-out-of-bounds_in_mm/page_isolation.c
Date: Tue, 10 May 2022 14:19:04 -0700 [thread overview]
Message-ID: <20220510141904.242d9301d109d413ea10e978@linux-foundation.org> (raw)
In-Reply-To: <20220510095824.GB3969@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Tue, 10 May 2022 17:58:24 +0800 kernel test robot <oliver.sang@intel.com> wrote:
> commit: 23e12fc477f1c2729af51c427087e777d6e63803 ("mm: make alloc_contig_range work at pageblock granularity")
> https://github.com/hnaz/linux-mm master
That tree is no longer being updated. Please switch to
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Either the mm-unstable branch (hotfixes and MM) or the mm-everything
branch (mm-unstable plus non-MM patches).
mm-unstable includes
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-make-alloc_contig_range-work-at-pageblock-granularity-fix.patch,
which quite possibly fixes the issue you have detected.
Thanks.
next prev parent reply other threads:[~2022-05-10 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:58 [mm] 23e12fc477: UBSAN:shift-out-of-bounds_in_mm/page_isolation.c kernel test robot
2022-05-10 9:58 ` kernel test robot
2022-05-10 14:30 ` Zi Yan
2022-05-10 14:30 ` Zi Yan
2022-05-10 21:19 ` Andrew Morton [this message]
2022-05-10 21:19 ` Andrew Morton
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=20220510141904.242d9301d109d413ea10e978@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=oliver.sang@intel.com \
--cc=osalvador@suse.de \
--cc=renzhengeek@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.