From: Kees Cook <kees@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kees Cook <kees@kernel.org>,
andy@kernel.org, trondmy@kernel.org, anna@kernel.org,
gregkh@linuxfoundation.org, linux-hardening@vger.kernel.org,
linux-mm@kvack.org, linux-nfs@vger.kernel.org
Subject: Re: (subset) [PATCH -next v3 1/3] lib/string_choices: Add str_true_false()/str_false_true() helper
Date: Thu, 5 Sep 2024 09:51:14 -0700 [thread overview]
Message-ID: <172555507039.1959022.16303899697737520578.b4-ty@kernel.org> (raw)
In-Reply-To: <20240828132509.4447ff09665fa0d7b8020294@linux-foundation.org>
On Wed, 28 Aug 2024 13:25:09 -0700, Andrew Morton wrote:
> On Wed, 28 Aug 2024 11:49:51 +0800 Hongbo Li <lihongbo22@huawei.com> wrote:
>
> > > Anything which is calling these functions is not performance-sensitive,
> > > so optimizing for space is preferred. An out-of-line function which
> > > returns a const char * will achieve this?
> > I think this helper can achieve this. Because it is tiny enough, the
> > compiler will handle this like #define macro (do the replacement)
> > without allocating extra functional stack. On the contrary, if it is
> > implemented as a non-inline function, it will cause extra functional
> > stack when it was called every time. And it also should be implemented
> > in a source file (.c file), not in header file(.h file).
>
> [...]
Since I've taken over string maintainership, I've applied this to my
tree (where other similar changes are appearing). This should reduce
conflicts here...
Applied to for-next/hardening, thanks!
[1/3] lib/string_choices: Add str_true_false()/str_false_true() helper
https://git.kernel.org/kees/c/6ff4cd1160af
Take care,
--
Kees Cook
next prev parent reply other threads:[~2024-09-05 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 2:45 [PATCH -next v3 0/3] " Hongbo Li
2024-08-27 2:45 ` [PATCH -next v3 1/3] lib/string_choices: " Hongbo Li
2024-08-27 23:42 ` Andrew Morton
2024-08-28 1:48 ` Hongbo Li
2024-08-28 3:22 ` Andrew Morton
2024-08-28 3:49 ` Hongbo Li
2024-08-28 20:25 ` Andrew Morton
2024-08-29 1:12 ` Hongbo Li
2024-09-05 16:51 ` Kees Cook [this message]
2024-08-28 12:59 ` Andy Shevchenko
2024-08-27 2:45 ` [PATCH -next v3 2/3] mm: make use of str_true_false helper Hongbo Li
2024-08-27 2:45 ` [PATCH -next v3 3/3] nfs make use of str_false_true helper Hongbo Li
2024-08-27 3:33 ` Matthew Wilcox
2024-08-27 6:15 ` Hongbo Li
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=172555507039.1959022.16303899697737520578.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=anna@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lihongbo22@huawei.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.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