From: Oscar Salvador <osalvador@suse.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Matthew Wilcox <willy@infradead.org>,
Oscar Salvador <OSalvador@suse.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Michal Hocko <mhocko@suse.com>,
rong.a.chen@intel.com
Subject: Re: [RFC PATCH] mm, memory_hotplug: fix off-by-one in is_pageblock_removable
Date: Wed, 20 Feb 2019 09:33:47 +0100 [thread overview]
Message-ID: <20190220083343.g5hdxxmekqsjwo63@d104.suse.de> (raw)
In-Reply-To: <20190218181544.14616-1-mhocko@kernel.org>
On Mon, Feb 18, 2019 at 07:15:44PM +0100, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
> Fixes: efad4e475c31 ("mm, memory_hotplug: is_mem_section_removable do not pass the end of a zone")
> Reported-by: <rong.a.chen@intel.com>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
Looks good to me.
I glanced quickly over the memhotplug code and I did not see any other place
that could trigger the same problem.
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE L3
WARNING: multiple messages have this Message-ID (diff)
From: Oscar Salvador <osalvador@suse.de>
To: lkp@lists.01.org
Subject: Re: [RFC PATCH] mm, memory_hotplug: fix off-by-one in is_pageblock_removable
Date: Wed, 20 Feb 2019 09:33:47 +0100 [thread overview]
Message-ID: <20190220083343.g5hdxxmekqsjwo63@d104.suse.de> (raw)
In-Reply-To: <20190218181544.14616-1-mhocko@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On Mon, Feb 18, 2019 at 07:15:44PM +0100, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
> Fixes: efad4e475c31 ("mm, memory_hotplug: is_mem_section_removable do not pass the end of a zone")
> Reported-by: <rong.a.chen@intel.com>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
Looks good to me.
I glanced quickly over the memhotplug code and I did not see any other place
that could trigger the same problem.
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2019-02-20 8:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 5:28 [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI kernel test robot
2019-02-18 5:28 ` kernel test robot
2019-02-18 7:08 ` [LKP] " Michal Hocko
2019-02-18 7:08 ` Michal Hocko
2019-02-18 8:47 ` [LKP] " Rong Chen
2019-02-18 8:47 ` Rong Chen
2019-02-18 9:03 ` [LKP] " Michal Hocko
2019-02-18 9:03 ` Michal Hocko
2019-02-18 9:11 ` [LKP] " Rong Chen
2019-02-18 9:11 ` Rong Chen
2019-02-18 9:29 ` [LKP] " Michal Hocko
2019-02-18 9:29 ` Michal Hocko
2019-02-18 8:55 ` [LKP] " Michal Hocko
2019-02-18 8:55 ` Michal Hocko
2019-02-18 10:01 ` [LKP] " Rong Chen
2019-02-18 10:01 ` Rong Chen
2019-02-18 10:30 ` [LKP] " Michal Hocko
2019-02-18 10:30 ` Michal Hocko
2019-02-18 14:05 ` [LKP] " Mike Rapoport
2019-02-18 15:20 ` Michal Hocko
2019-02-18 15:20 ` Michal Hocko
2019-02-18 15:22 ` [LKP] " Michal Hocko
2019-02-18 15:22 ` Michal Hocko
2019-02-18 16:48 ` [LKP] " Mike Rapoport
2019-02-18 17:05 ` Michal Hocko
2019-02-18 17:05 ` Michal Hocko
2019-02-18 17:48 ` [LKP] " Mike Rapoport
2019-02-18 17:57 ` Matthew Wilcox
2019-02-18 17:57 ` Matthew Wilcox
2019-02-18 18:11 ` [LKP] " Michal Hocko
2019-02-18 18:11 ` Michal Hocko
2019-02-18 19:05 ` [LKP] " Matthew Wilcox
2019-02-18 19:05 ` Matthew Wilcox
2019-02-18 18:15 ` [RFC PATCH] mm, memory_hotplug: fix off-by-one in is_pageblock_removable Michal Hocko
2019-02-18 18:15 ` Michal Hocko
2019-02-18 18:31 ` Mike Rapoport
2019-02-20 8:33 ` Oscar Salvador [this message]
2019-02-20 8:33 ` Oscar Salvador
2019-02-20 12:57 ` Michal Hocko
2019-02-20 12:57 ` Michal Hocko
2019-02-21 3:18 ` [LKP] " Rong Chen
2019-02-21 3:18 ` Rong Chen
2019-02-21 7:25 ` [LKP] " Michal Hocko
2019-02-21 7:25 ` Michal Hocko
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=20190220083343.g5hdxxmekqsjwo63@d104.suse.de \
--to=osalvador@suse.de \
--cc=OSalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=rong.a.chen@intel.com \
--cc=rppt@linux.ibm.com \
--cc=willy@infradead.org \
/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.