From: Matthew Wilcox <willy@infradead.org>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xattr: switch to vmemdup_user()
Date: Thu, 4 Mar 2021 12:17:55 +0000 [thread overview]
Message-ID: <20210304121755.GJ2723601@casper.infradead.org> (raw)
In-Reply-To: <1614666741-16796-1-git-send-email-yang.lee@linux.alibaba.com>
On Tue, Mar 02, 2021 at 02:32:21PM +0800, Yang Li wrote:
> Replace opencoded alloc and copy with vmemdup_user()
>
> fixed the following coccicheck:
> ./fs/xattr.c:561:11-19: WARNING opportunity for vmemdup_user
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
next prev parent reply other threads:[~2021-03-04 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 6:32 [PATCH] xattr: switch to vmemdup_user() Yang Li
2021-03-04 12:17 ` Matthew Wilcox [this message]
2021-09-29 21:20 ` kernel test robot
2021-09-29 22:38 ` kernel test robot
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=20210304121755.GJ2723601@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yang.lee@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).