From: Michal Hocko <mhocko@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: Alastair D'Silva <alastair@d-silva.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
Mike Rapoport <rppt@linux.ibm.com>, Baoquan He <bhe@redhat.com>,
Wei Yang <richard.weiyang@gmail.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 1/3] mm: Trigger bug on if a section is not found in __section_nr
Date: Fri, 28 Jun 2019 13:58:51 +0200 [thread overview]
Message-ID: <20190628115851.GH2751@dhcp22.suse.cz> (raw)
In-Reply-To: <634a6b8e-3113-f0af-f8d3-9b766f8cd376@redhat.com>
On Fri 28-06-19 13:37:07, David Hildenbrand wrote:
> VM_BUG_ON is only really active with CONFIG_DEBUG_VM. On
> !CONFIG_DEBUG_VM it translated to BUILD_BUG_ON_INVALID(), which is a
> compile-time only check.
>
> Or am I missing something?
You are not missing anything.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-06-28 11:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 6:11 [PATCH v2 0/3] mm: Cleanup & allow modules to hotplug memory Alastair D'Silva
2019-06-26 6:11 ` [PATCH v2 1/3] mm: Trigger bug on if a section is not found in __section_nr Alastair D'Silva
2019-06-26 6:21 ` Michal Hocko
2019-06-26 6:27 ` Alastair D'Silva
2019-06-26 6:57 ` Michal Hocko
2019-06-27 0:50 ` Alastair D'Silva
2019-06-27 8:10 ` Michal Hocko
2019-06-28 0:46 ` Alastair D'Silva
2019-07-01 10:46 ` Michal Hocko
2019-07-02 4:13 ` Alastair D'Silva
2019-07-02 6:13 ` Michal Hocko
2019-07-02 6:16 ` Alastair D'Silva
2019-06-28 11:37 ` David Hildenbrand
2019-06-28 11:58 ` Michal Hocko [this message]
2019-06-26 6:11 ` [PATCH v2 2/3] mm: don't hide potentially null memmap pointer in sparse_remove_one_section Alastair D'Silva
2019-06-26 6:23 ` Michal Hocko
2019-06-26 6:30 ` Alastair D'Silva
2019-06-26 6:59 ` Michal Hocko
2019-06-28 11:29 ` David Hildenbrand
2019-06-26 6:11 ` [PATCH v2 3/3] mm: Don't manually decrement num_poisoned_pages Alastair D'Silva
2019-06-26 6:24 ` Michal Hocko
2019-06-28 11:29 ` David Hildenbrand
2019-06-26 7:57 ` [PATCH v2 0/3] mm: Cleanup & allow modules to hotplug memory Christoph Hellwig
2019-06-27 0:51 ` Alastair D'Silva
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=20190628115851.GH2751@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alastair@d-silva.org \
--cc=bhe@redhat.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=rafael@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=rppt@linux.ibm.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