[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALOAHbC0ta-g2pcWqsL6sVVigthedN04y8_tH-cS9TuDGEBsEg@mail.gmail.com>
Date: Sun, 23 Jun 2024 10:29:30 +0800
From: Yafang Shao <laoar.shao@...il.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: torvalds@...ux-foundation.org, ebiederm@...ssion.com,
alexei.starovoitov@...il.com, rostedt@...dmis.org, catalin.marinas@....com,
akpm@...ux-foundation.org, penguin-kernel@...ove.sakura.ne.jp,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, audit@...r.kernel.org,
linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
bpf@...r.kernel.org, netdev@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v3 06/11] mm/util: Deduplicate code in {kstrdup,kstrndup,kmemdup_nul}
On Fri, Jun 21, 2024 at 9:57 PM Matthew Wilcox <willy@...radead.org> wrote:
>
> On Fri, Jun 21, 2024 at 10:29:54AM +0800, Yafang Shao wrote:
> > +++ b/mm/internal.h
>
> Why are you putting __kstrndup in a header file when it's only used
> in util.c?
I want to make it always inlined. However, it is not recommended to
define an inline function in a .c file, right ?
>
> Also, I think this function is actually __kmemdup_nul(), not
> __kstrndup().
>
Good suggestion. Will use __kmemdup_nul() instead.
--
Regards
Yafang
Powered by blists - more mailing lists