From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexei Starovoitov Subject: Re: [PATCH v2 net-next 1/2] lib: introduce strncpy_from_unsafe() Date: Fri, 28 Aug 2015 15:08:35 -0700 Message-ID: <55E0DBE3.8010504@plumgrid.com> References: <1440791509-5450-1-git-send-email-ast@plumgrid.com> <1440791509-5450-2-git-send-email-ast@plumgrid.com> <20150828174813.23e6e78b@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Ingo Molnar , Masami Hiramatsu , Wang Nan , He Kuang , Daniel Borkmann , Brendan Gregg , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Steven Rostedt Return-path: In-Reply-To: <20150828174813.23e6e78b@gandalf.local.home> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 8/28/15 2:48 PM, Steven Rostedt wrote: >> * On success, returns the length of the string (not including the trailing >> >+ * NUL). > I think it includes the NUL. oops. yes. that was a copy paste from strncpy_from_user comment. trace_kprobe usage wants NUL to be counted, so I intended to have it counted, but that brings the question what should be the semantics. Should it be similar to strncpy_from_user (not counting NUL) or similar to strlen_user (counts NUL) ? imo counting NUL makes a little bit more sense, since when a user says strncpy_from_unsafe(..., ..., 32) and it returns 32 as the whole buffer was filled, it looks cleaner. Thoughts?