From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Andrey Skvortsov <andrej.skvortzov@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: do not export const kfree and kstrdup variants
Date: Tue, 24 Sep 2024 14:08:27 +0900 [thread overview]
Message-ID: <20240924050827.GA676153@google.com> (raw)
In-Reply-To: <20240924050351.675925-1-senozhatsky@chromium.org>
On (24/09/24 14:03), Sergey Senozhatsky wrote:
> Both kfree_const() and kstrdup_const() use __start_rodata
> and __end_rodata, which do not work for modules. This is
> especially important for kfree_const(). Stop exporting
> these functions, as they cannot be used in the modules.
... and of course I forgot to commit the kstrdup_const() part.
Let me resend.
prev parent reply other threads:[~2024-09-24 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 5:03 Sergey Senozhatsky
2024-09-24 5:08 ` Sergey Senozhatsky [this message]
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=20240924050827.GA676153@google.com \
--to=senozhatsky@chromium.org \
--cc=a.hajda@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=andrej.skvortzov@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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