linux-kernel - Re: Implement character sets for sscanf()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160222193921.GD31460@packer-debian-8-amd64.digitalocean.com>
Date:	Mon, 22 Feb 2016 14:39:21 -0500
From:	Jessica Yu <jeyu@...hat.com>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Rasmus Villemoes <linux@...musvillemoes.dk>,
	Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org
Subject: Re: Implement character sets for sscanf()

+++ Andy Shevchenko [22/02/16 11:27 +0200]:
>On Fri, 2016-02-19 at 20:20 -0500, Jessica Yu wrote:
>> Hi,
>>
>> This patch adds support for the '%[' conversion specifier for
>> sscanf().
>> Since functions that calculate substring lengths based on accepted or
>> rejected characters already exist in the kernel (namely strspn() and
>> strcspn()), it's not much of a stretch to add some basic support for
>> the
>> bracket '%[' conversion specifier for sscanf(). This is useful in
>> cases
>> where we'd like to match substrings delimited by something other than
>> spaces. The original motivation for this patch actually came from
>> livepatch
>> (https://lkml.org/lkml/2016/2/8/790), where we were trying to come up
>> with
>> a clean way to parse symbol names with substrings delimited by
>> periods and
>> commas.
>>
>> Patch based on linux-next-20160219.
>>
>> Here are some test cases:
>
>Test cases should land into lib/test_scanf.c and be submitted as a
>separate patch.
>
>Also, you have something misconfigured when you sent patches. git-send-
>email usually does a perfect job.

Thanks for the tip. Yeah, I had a small hiccup with git-send-email,
which is why the patchset came out like that :-\ In any case, the
attached test cases are more for the benefit of the patch reviewer,
not something I intended to be merged. For v2, I will just send the
single patch out.

Jessica