From: Tejun Heo <tj@kernel.org>
To: "lilingfeng (A)" <lilingfeng3@huawei.com>
Cc: linux-kernel@vger.kernel.org, jack@suse.cz,
bingjingc@synology.com, ebiggers@google.com,
james.smart@broadcom.com, houtao1@huawei.com,
yi.zhang@huawei.com, yangerkun@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH-next v2] lib: parser: optimize match_NUMER apis to use local array
Date: Tue, 10 Jan 2023 07:25:40 -1000 [thread overview]
Message-ID: <Y72flHV4lsxUi5/T@slm.duckdns.org> (raw)
In-Reply-To: <f0af597f-0c56-87e1-995a-e0c55e645f7e@huawei.com>
On Tue, Jan 10, 2023 at 09:49:21PM +0800, lilingfeng (A) wrote:
>
> 在 2022/12/13 22:17, Li Lingfeng 写道:
> > Memory will be allocated to store substring_t in match_strdup(), which means
> > the caller of match_strdup() may need to be scheduled out to wait for reclaiming
> > memory.
> >
> > Using local array to store substring_t to remove the restriction.
> >
> > Link: https://lore.kernel.org/all/20221104023938.2346986-5-yukuai1@huaweicloud.com/
> > Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
> > ---
> > v1->v2:
> > change the name of buffer's length
> > use match_strlcpy() to copy string and keep string length check
> > lib/parser.c | 42 +++++++++++++++++++++++-------------------
> > 1 file changed, 23 insertions(+), 19 deletions(-)
> >
> > diff --git a/lib/parser.c b/lib/parser.c
>
> I can't find the maintainer of this module through the script, does anyone
> know?
Oh, send it to Andrew Morton <akpm@linux-foundation.org>.
Thanks.
--
tejun
prev parent reply other threads:[~2023-01-10 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 14:17 Li Lingfeng
2022-12-15 16:55 ` Tejun Heo
2023-01-10 13:49 ` lilingfeng (A)
2023-01-10 17:25 ` Tejun Heo [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=Y72flHV4lsxUi5/T@slm.duckdns.org \
--to=tj@kernel.org \
--cc=bingjingc@synology.com \
--cc=ebiggers@google.com \
--cc=houtao1@huawei.com \
--cc=jack@suse.cz \
--cc=james.smart@broadcom.com \
--cc=lilingfeng3@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®