[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <95819052.15033.1713816660761.JavaMail.zimbra@nod.at>
Date: Mon, 22 Apr 2024 22:11:00 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
kent overstreet <kent.overstreet@...ux.dev>,
SeongJae Park <sj@...nel.org>,
anton ivanov <anton.ivanov@...bridgegreys.com>,
Johannes Berg <johannes@...solutions.net>,
linux-mm <linux-mm@...ck.org>,
linux-um <linux-um@...ts.infradead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc
----- Ursprüngliche Mail -----
> Von: "Suren Baghdasaryan" <surenb@...gle.com>
> Betreff: [PATCH 1/1] arch/um: fix forward declaration for vmalloc
> Patch [1] replaced vmalloc() function with a new definition but it did
> not adjust the forward declaration used in UML architecture. Change it
> to act as before.
> Note that this prevents the vmalloc() allocations in __wrap_malloc()
> from being accounted. If accounting here is critical, we will have
> to remove this forward declaration and include vmalloc.h, however
> that would pull in more dependencies and would require introducing more
> architecture-specific headers, like asm/bug.h, asm/rwonce.h, etc.
> This is likely the reason why this forward declaration was introduced
> in the first place.
>
> [1] https://lore.kernel.org/all/20240321163705.3067592-31-surenb@google.com/
>
> Fixes: 576477564ede ("mm: vmalloc: enable memory allocation profiling")
This commit id is not in Linus tree.
Do I miss something?
Thanks,
//richard
Powered by blists - more mailing lists