[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180831154818.9D0E96038E@smtp.codeaurora.org>
Date: Fri, 31 Aug 2018 15:48:18 +0000 (UTC)
From: Kalle Valo <kvalo@...eaurora.org>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH] brcmfmac: fix wrong strnchr usage
Rasmus Villemoes <linux@...musvillemoes.dk> wrote:
> strnchr takes arguments in the order of its name: string, max bytes to
> read, character to search for. Here we're passing '\n' aka 10 as the
> buffer size, and searching for sizeof(buf) aka BRCMF_DCMD_SMLEN aka
> 256 (aka '\0', since it's implicitly converted to char) within those 10
> bytes.
>
> Just interchanging the last two arguments would still leave a bug,
> because if we've been successful once, there are not sizeof(buf)
> characters left after the new value of p.
>
> Since clmver is immediately afterwards passed as a %s argument, I assume
> that it is actually a properly nul-terminated string. For that case, we
> have strreplace().
>
> Signed-off-by: Rasmus Villemoes <linux@...musvillemoes.dk>
Patch applied to wireless-drivers-next.git, thanks.
cb18e2e9ec71 brcmfmac: fix wrong strnchr usage
--
https://patchwork.kernel.org/patch/10572951/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists