[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180326141717epcms5p4064a0fd4f594b2ff434f9b05cd1ea5ad@epcms5p4>
Date: Mon, 26 Mar 2018 19:47:17 +0530
From: Vaneet Narang <v.narang@...sung.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Maninder Singh <maninder1.s@...sung.com>
CC: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Philippe Ombredanne <pombredanne@...b.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Michal Hocko <mhocko@...e.com>,
"vinmenon@...eaurora.org" <vinmenon@...eaurora.org>,
"gomonovych@...il.com" <gomonovych@...il.com>,
Ayush Mittal <ayush.m@...sung.com>,
LKML <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Linux-MM <linux-mm@...ck.org>,
AMIT SAHRAWAT <a.sahrawat@...sung.com>,
PANKAJ MISHRA <pankaj.m@...sung.com>
Subject: RE: Re: [PATCH v2] mm/page_owner: ignore everything below the IRQ
entry point
Hi Dmitry,
>Every user of stack_depot should filter out irq frames, without that
>stack_depot will run out of memory sooner or later. so this is a
>change in the right direction.
>
>Do we need to define empty version of in_irqentry_text? Shouldn't only
>filter_irq_stacks be used by kernel code?
We thought about this but since we were adding both the APIs filter_irq_stacks & in_irqentry_text
in header file so we thought of defining empty definition for both as both the APIs are accessible
to the module who is going to include header file.
If you think empty definition of in_irqentry_text() is not requited then we will modify & resend the
patch.
Thanks & Regards,
Vaneet Narang
Powered by blists - more mailing lists