linux-kernel - Re: [PATCH v3] add u64 number parser

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: <CAADWXX9cJLw2y61rOe0Bd2usCUcPOPrjFcvPXfhKXyk9vDTRHQ@mail.gmail.com>
Date:   Sat, 24 Sep 2016 11:31:11 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     James Smart <james.smart@...adcom.com>
Cc:     lkml <linux-kernel@...r.kernel.org>,
        linux-nvme@...ts.infradead.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v3] add u64 number parser

On Sat, Sep 24, 2016 at 8:27 AM, James Smart <james.smart@...adcom.com> wrote:
>
> add u64 number parser
>
> Prior patch revised to use kasprintf.
> Modified match_number to use kasprintf as well

Why would you do this? It's insane. kasprintf() is not the right thing
at all to use for anything like this. It appears that you want to use
strncpy() or something. Or you could just avoid the extra copy
entirely in 99% of all cases and just use simple_strtol() and check
that the end didn't overflow the substring, which it presumably never
does anyway.

Yes, the stupid code is already disgustingly bad. But let's not make
it *worse*, for chrissake!

               Linus