Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 25 Feb 2019 15:15:33 +1100
From: "Tobin C. Harding" <>
To: Kees Cook <>
Cc: "Tobin C. Harding" <>,
	Jann Horn <>,
	Andy Shevchenko <>,
	Randy Dunlap <>,
	Rasmus Villemoes <>,
	Stephen Rothwell <>,
	Andy Lutomirski <>,
	Daniel Micay <>,
	Arnd Bergmann <>,
	Miguel Ojeda <>,
	"Gustavo A. R. Silva" <>,
	Shuah Khan <>,
	Greg Kroah-Hartman <>,
	Alexander Shishkin <>,,
Subject: [PATCH v2 0/1] lib/string: Add strscpy_pad() function


This patch set was formerly

	Subject: [PATCH 0/6] lib: Add safe string funtions[sic]

And FTR can be seen here:

The v1 patch set has been reduced to a single patch by dropping the
strscpy_from_user() stuff and by rolling all the docs changes into the
main patch as suggested.

This patch adds the function strscpy_pad() named after consensus was
reached on the v1 email thread (linked to above).

Thanks to Kees for the extreme test case coverage.  test_basic() is
probably redundant but is left in for the benefit of any poor sucker who
has to debug a regression using test_fully().

The test module is _not_ tied into kselftest.  As discussed on v1, there
are some issues with tools/testing/selftest/lib/ at the moment.  I intend
on working on those issues as suggested but it does not seem totally
relevant to this patch so instead of slowing this one down with my poor
knowledge of how kselftest works it seems better to do this separately. 

thanks for looking at this,

Tobin C. Harding (1):
  lib/string: Add strscpy_pad() function

 include/linux/string.h |   4 +
 lib/Kconfig.debug      |   3 +
 lib/Makefile           |   1 +
 lib/string.c           |  47 +++++++++--
 lib/test_strscpy.c     | 175 +++++++++++++++++++++++++++++++++++++++++
 5 files changed, 223 insertions(+), 7 deletions(-)
 create mode 100644 lib/test_strscpy.c


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.