On 27.08.2011 20:28, Joerg Sonnenberger wrote: > On Sat, Aug 27, 2011 at 08:13:28PM +0200, Jean-Yves Migeon wrote: >> On 27.08.2011 19:57, Reinoud Zandijk wrote: >>> Fix copystring routines to NOT just copy all since not all space might be >>> writable. This can be fixed by implementing/importing strnlen(3) in the >>> kernel >> >> Any reason no to? If there's none, I can do it. >> >> At first sight it's straightforward to add to common/, and I am more at >> peace knowing that we have a "valid" strnlen() in kernel rather than a >> bogus macro that may spread elsewhere... > > Or it could use memchr for that same purpose.
Right; note that the question about strnlen(3) remains valid though: strlen/strnlen appear in the same man page. So one's could expect to have both accessible, even in kernel. -- Jean-Yves Migeon jeanyves.mig...@free.fr
