[<prev] [next>] [day] [month] [year] [list]
Message-ID: <a0f76fa8a8ffd41e9f11a86ab6309b0f426966a8.camel@suse.com>
Date: Fri, 9 Aug 2019 08:19:47 +0000
From: Martin Wilck <Martin.Wilck@...e.com>
To: "zhongjiang@...wei.com" <zhongjiang@...wei.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"opensource@...ayne.com" <opensource@...ayne.com>,
"wang6495@....edu" <wang6495@....edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"swinslow@...il.com" <swinslow@...il.com>,
"saurav.girepunje@...il.com" <saurav.girepunje@...il.com>
CC: "saurav.girepunje@...mail.com" <saurav.girepunje@...mail.com>
Subject: Re: [PATCH] cdrom: gdrom.c: fix a incorrect use of kstrndup()
On Tue, 2019-08-06 at 00:11 +0530, Saurav Girepunje wrote:
> According to doc: "Note: Use kmemdup_nul() instead if the size
> is known exactly." So we should use kmemdup_nul() here instead of
> kstrndup().
>
> Signed-off-by: Saurav Girepunje <saurav.girepunje@...il.com>
> ---
Reviewed-by: Martin Wilck <mwilck@...e.com>
Powered by blists - more mailing lists