From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: "Mirsad Todorovac" <mtodorovac69@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Victor Skvortsov" <victor.skvortsov@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>,
"Xinhui Pan" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Carlos Maiolino" <cem@kernel.org>,
"Chandan Babu R" <chandanbabu@kernel.org>,
"Dave Chinner" <dchinner@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v1 2/3] xfs/libxfs: replace kmalloc() and memcpy() with kmemdup()
Date: Mon, 6 Jan 2025 11:37:06 -0800 [thread overview]
Message-ID: <20250106193706.GG6174@frogsfrogsfrogs> (raw)
In-Reply-To: <cdnpycsyf37gbcp6yxx36pxgilothhdpajmtwle5pphjxshn6o@j5enpjtww3xx>
On Sun, Dec 29, 2024 at 01:58:19PM +0100, Andrey Albershteyn wrote:
> On 2024-12-18 16:35:21, Darrick J. Wong wrote:
> > On Tue, Dec 17, 2024 at 11:58:12PM +0100, Mirsad Todorovac wrote:
> > > The source static analysis tool gave the following advice:
> > >
> > > ./fs/xfs/libxfs/xfs_dir2.c:382:15-22: WARNING opportunity for kmemdup
> > >
> > > → 382 args->value = kmalloc(len,
> > > 383 GFP_KERNEL | __GFP_NOLOCKDEP | __GFP_RETRY_MAYFAIL);
> > > 384 if (!args->value)
> > > 385 return -ENOMEM;
> > > 386
> > > → 387 memcpy(args->value, name, len);
> > > 388 args->valuelen = len;
> > > 389 return -EEXIST;
> > >
> > > Replacing kmalloc() + memcpy() with kmemdump() doesn't change semantics.
> > > Original code works without fault, so this is not a bug fix but proposed improvement.
> >
> > I guess this is all right, but seeing as this code is shared with
> > userspace ("libxfs"), making this change will just add to the wrappers
> > that we have to have:
> >
> > void *kmemdup_noprof(const void *src, size_t len, gfp_t gfp)
> > {
> > void *p;
> >
> > p = kmalloc_node_track_caller_noprof(len, gfp, NUMA_NO_NODE, _RET_IP_);
> > if (p)
> > memcpy(p, src, len);
> > return p;
> > }
> >
> > Is this sufficiently better? That's a question for the kernel
> > maintainer (cem) and the userspace maintainer (andrey, now cc'd).
> >
> > --D
>
> There's still possibility to set wrong length in args->valuelen,
> which I suppose what this change tries to prevent.
>
> But otherwise wrapper looks good to me
Ok, proceed then.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> >
> > > Link: https://lwn.net/Articles/198928/
> > > Fixes: 94a69db2367ef ("xfs: use __GFP_NOLOCKDEP instead of GFP_NOFS")
> > > Fixes: 384f3ced07efd ("[XFS] Return case-insensitive match for dentry cache")
> > > Fixes: 2451337dd0439 ("xfs: global error sign conversion")
> > > Cc: Carlos Maiolino <cem@kernel.org>
> > > Cc: "Darrick J. Wong" <djwong@kernel.org>
> > > Cc: Chandan Babu R <chandanbabu@kernel.org>
> > > Cc: Dave Chinner <dchinner@redhat.com>
> > > Cc: linux-xfs@vger.kernel.org
> > > Cc: linux-kernel@vger.kernel.org
> > > Signed-off-by: Mirsad Todorovac <mtodorovac69@gmail.com>
> > > ---
> > > v1:
> > > initial version.
> > >
> > > fs/xfs/libxfs/xfs_dir2.c | 3 +--
> > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/fs/xfs/libxfs/xfs_dir2.c b/fs/xfs/libxfs/xfs_dir2.c
> > > index 202468223bf9..24251e42bdeb 100644
> > > --- a/fs/xfs/libxfs/xfs_dir2.c
> > > +++ b/fs/xfs/libxfs/xfs_dir2.c
> > > @@ -379,12 +379,11 @@ xfs_dir_cilookup_result(
> > > !(args->op_flags & XFS_DA_OP_CILOOKUP))
> > > return -EEXIST;
> > >
> > > - args->value = kmalloc(len,
> > > + args->value = kmemdup(name, len,
> > > GFP_KERNEL | __GFP_NOLOCKDEP | __GFP_RETRY_MAYFAIL);
> > > if (!args->value)
> > > return -ENOMEM;
> > >
> > > - memcpy(args->value, name, len);
> > > args->valuelen = len;
> > > return -EEXIST;
> > > }
> > > --
> > > 2.43.0
> > >
> > >
> >
>
> --
> - Andrey
>
>
next prev parent reply other threads:[~2025-01-06 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241217225811.2437150-2-mtodorovac69@gmail.com>
2024-12-17 22:58 ` [PATCH v1 2/3] xfs/libxfs: replace kmalloc() and memcpy() with kmemdup() Mirsad Todorovac
2024-12-19 0:35 ` Darrick J. Wong
2024-12-29 12:58 ` Andrey Albershteyn
2025-01-06 19:37 ` Darrick J. Wong [this message]
2025-01-09 8:49 ` Carlos Maiolino
2025-01-14 10:28 ` Carlos Maiolino
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=20250106193706.GG6174@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=Xinhui.Pan@amd.com \
--cc=aalbersh@redhat.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dchinner@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mtodorovac69@gmail.com \
--cc=simona@ffwll.ch \
--cc=victor.skvortsov@amd.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