[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <28177f7f7c1d48b30338071f57f9801d45617f8b.camel@mediatek.com>
Date: Wed, 13 Jul 2022 17:42:22 +0800
From: Chunfeng Yun <chunfeng.yun@...iatek.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Matthias Brugger <matthias.bgg@...il.com>,
<linux-usb@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, Felipe Balbi <balbi@...nel.org>,
Eddie Hung <eddie.hung@...iatek.com>
Subject: Re: [PATCH 1/5] usb: mtu3: fix coverity of string buffer
On Mon, 2022-07-11 at 08:45 +0200, Greg Kroah-Hartman wrote:
> On Mon, Jul 11, 2022 at 02:39:10PM +0800, Chunfeng Yun wrote:
> > On Fri, 2022-07-08 at 09:26 +0200, Greg Kroah-Hartman wrote:
> > > On Fri, Jul 08, 2022 at 03:18:59PM +0800, Chunfeng Yun wrote:
> > > > Use snprintf instead of sprintf which could cause buffer
> > > > overflow.
> > >
> > > How can it cause an overflow?
> >
> > Maybe I didn't describe it clearly, this patch is used to fix
> > coverity
> > check warning of string buffer, in fact no overflow happens.
>
> Then perhaps the coverity warning is useless and
> yet-another-false-positive that that tool is known to spit out?
>
> Don't make code changes just because broken tools say to do so.
Got it, thanks a lot
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists