[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZIPCIpWPQbVqoI4q@casper.infradead.org>
Date: Sat, 10 Jun 2023 01:21:54 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Wei-chin Tsai (蔡維晉)
<Wei-chin.Tsai@...iatek.com>
Cc: "linux@...linux.org.uk" <linux@...linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mel Lee (李奇錚) <Mel.Lee@...iatek.com>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
wsd_upstream <wsd_upstream@...iatek.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
Ivan Tseng (曾志軒)
<ivan.tseng@...iatek.com>,
"angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH v1 1/1] memory: export symbols for process memory related
functions
On Fri, Jun 09, 2023 at 04:09:01PM +0000, Wei-chin Tsai (蔡維晉) wrote:
> > You haven't included any users of these new exports, so the initial
> > reaction is going to be negative - please include the users of these
> > new symbols in your patch set.
> We use these two export functions from our kernel module to get a
> specific user process's memory information and heap usage. Furthermore,
> we can use such information to detect the memory leak issues.
>
> The example code is as follows:
No. You need to be submitting the code that will use the symbol *at the
same time* as the patch to export the symbol. No example code showing
how it could be used. Because if the user isn't compelling, the patch
to export the symbol won't be applied either.
Powered by blists - more mailing lists