From: Richard Weinberger <richard@nod.at>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kent overstreet <kent.overstreet@linux.dev>,
SeongJae Park <sj@kernel.org>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-mm <linux-mm@kvack.org>,
linux-um <linux-um@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc
Date: Mon, 22 Apr 2024 22:11:00 +0200 (CEST) [thread overview]
Message-ID: <95819052.15033.1713816660761.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20240326073750.726636-1-surenb@google.com>
----- Ursprüngliche Mail -----
> Von: "Suren Baghdasaryan" <surenb@google.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
next prev parent reply other threads:[~2024-04-22 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 7:37 Suren Baghdasaryan
2024-03-26 15:37 ` SeongJae Park
2024-03-28 8:48 ` Johannes Berg
2024-04-22 20:11 ` Richard Weinberger [this message]
2024-04-22 20:19 ` Suren Baghdasaryan
2024-04-22 20:31 ` Richard Weinberger
2024-04-22 20:39 ` Suren Baghdasaryan
2024-04-22 20:50 ` Richard Weinberger
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=95819052.15033.1713816660761.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.org \
--cc=surenb@google.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