p71924506
/
linux_old1
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

test: firmware_class: use kstrndup() where appropriate 

We're essentially just doing an open-coded kstrndup(). The only
differences are with what happens after the first '\0' character, but
request_firmware() doesn't care about that.

Suggested-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
This commit is contained in:
Brian Norris 2015-12-09 14:50:26 -08:00 committed by Shuah Khan
parent 47e0bbb7fa
commit be4a1326d1
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
lib/test_firmware.c
View File

@ -54,10 +54,9 @@ static ssize_t trigger_request_store(struct device *dev,
int rc; int rc;
char *name; char *name;
name = kzalloc(count + 1, GFP_KERNEL); name = kstrndup(buf, count, GFP_KERNEL);
if (!name) if (!name)
return -ENOSPC; return -ENOSPC;
memcpy(name, buf, count);
pr_info("loading '%s'\n", name); pr_info("loading '%s'\n", name);