linux-kernel - Re: [dm-devel] [PATCH] dm-init: fix 2 incorrect use of kstrndup()

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <fcf2c3c0-e479-9e74-59d5-79cd2a0bade6@acm.org>
Date:   Wed, 29 May 2019 05:23:53 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     Gen Zhang <blackgod016574@...il.com>, agk@...hat.com,
        snitzer@...hat.com, dm-devel@...hat.com
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [dm-devel] [PATCH] dm-init: fix 2 incorrect use of kstrndup()

On 5/28/19 6:33 PM, Gen Zhang wrote:
> In drivers/md/dm-init.c, kstrndup() is incorrectly used twice.
> 
> It should be: char *kstrndup(const char *s, size_t max, gfp_t gfp);

Should the following be added to this patch?

Fixes: 6bbc923dfcf5 ("dm: add support to directly boot to a mapped
device") # v5.1.
Cc: stable

Thanks,

Bart.