From: Shuah Khan Subject: Re: [PATCH v2 2/5] test: firmware_class: use kstrndup() where appropriate Date: Thu, 7 Jan 2016 13:55:13 -0700 Message-ID: <568ED0B1.4060205@osg.samsung.com> References: <1449701429-121423-1-git-send-email-computersforpeace@gmail.com> <1449701429-121423-2-git-send-email-computersforpeace@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1449701429-121423-2-git-send-email-computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Brian Norris , Greg Kroah-Hartman , Ming Lei Cc: Kees Cook , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Luis R. Rodriguez" , Shuah Khan List-Id: linux-api@vger.kernel.org On 12/09/2015 03:50 PM, Brian Norris wrote: > 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 > Signed-off-by: Brian Norris > --- Thanks for fixing it. Applied to linux-kselftest next for 4.5-rc1. thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org | (970) 217-8978