[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <80df111f-8d34-f3c4-add5-4d041410b5a5@web.de>
Date: Sat, 11 Apr 2020 07:07:13 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Alexander Popov <alex.popov@...ux.com>, cocci@...teme.lip6.fr,
kernel-hardening@...ts.openwall.com
Cc: Jann Horn <jannh@...gle.com>, Julia Lawall <Julia.Lawall@...6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Kees Cook <keescook@...omium.org>,
Hans Verkuil <hverkuil@...all.nl>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-media@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Coccinelle rule for CVE-2019-18683
> Analysing each matching case would take a lot of time.
How many efforts would you like to invest in adjusting the situation?
Will any more development possibilities picked up to reduce the presentation
of false positives by the mentioned source code analysis approach considerably?
Regards,
Markus
Powered by blists - more mailing lists