Date: Thu, 18 Feb 2016 07:47:05 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Svyatoslav Razmyslov <razmyslov@viva64.com> Cc: Russell Haley <russ.haley@gmail.com>, Fehmi Noyan ISI <fnoyanisi@yahoo.com>, Andrey Karpov <karpov@viva64.com>, freebsd-doc@FreeBSD.org Subject: Re: Checking FreeBSD kernel with static analyzer Message-ID: <alpine.BSF.2.20.1602180738030.18482@wonkity.com> In-Reply-To: <56C5B3D5.5090608@viva64.com> References: <56C48E65.8040309@viva64.com> <909922573.4701692.1455746920523.JavaMail.yahoo@mail.yahoo.com> <56C57E08.5040207@viva64.com> <20160218082452.4382803.11148.3074@gmail.com> <56C5B3D5.5090608@viva64.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Feb 2016, Svyatoslav Razmyslov wrote: > I have sent the file in CSV format (PVS-Studio-log-freebsd.csv). Does it work > for you? > > 18.02.2016 11:24, Russell Haley пишет: >> Svyatoslav, >> >> Is there an output format for the issue report that could be massaged in >> python or lua or the like and submitted or imported through bugzilla? CSV, >> xml, json? The mailing list stripped the attachment, although the mail direct to me included it. The review has been of the text file. We can make the CSV available. Automated creation of bug reports from these results might not be too useful. Many are only suspected problems and turn out to be false positives. From owner-freebsd-doc@freebsd.org Thu Feb 18 16:54:28 2016 Return-Path: <owner-freebsd-doc@freebsd.org> Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 908B9AAC078 for <freebsd-doc@mailman.ysv.freebsd.org>; Thu, 18 Feb 2016 16:54:28 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 638276BC for <freebsd-doc@freebsd.org>; Thu, 18 Feb 2016 16:54:28 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-pf0-x231.google.com with SMTP id e127so34357017pfe.3 for <freebsd-doc@freebsd.org>; Thu, 18 Feb 2016 08:54:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:content-transfer-encoding:message-id:date :subject:from:to:cc; bh=NUF5517EDH6RgMI7eif3YKKEfF0zzH5LcDuKLoCNc4s=; b=bxOHFpW4NbAMHSiDLZfKEI+i3RmDWInJjupRocdSB3pOo/C5LJieu1k+QsUOsyMMkc YVU1z395JUTdLK2B0Le/sOTJ46+0kA2KZpnviG8k54UK7Xig4EGjlSkHp711E1DcXgy9 Ej/dqmXRMjFObTFgjrUMBBC/mib5C2gTeapT/XmxD4RcGfz216rgVpldIYe6Zk0WyqIl mNlJjeI4QXgjtbSk2T+JTGo6sstel+jgKrKx/fYLLQBjGdcdhtXHHitYk+y5I99NdxsT R+3/eM6FIvp8GiYLV7GfC2EY+pQrrq/o9+phtA9aPIfQiHxt7wPdCBB6VZl6boxBL1mj cauQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version :content-transfer-encoding:message-id:date:subject:from:to:cc; bh=NUF5517EDH6RgMI7eif3YKKEfF0zzH5LcDuKLoCNc4s=; b=ZdmTzrZIOXF6TPLVn8rVYJUTKR+qA+5KLkKhj9+CFBZhhhmoZCZWAzArH4laTOFsSu 93CubjlNYeNObtheGgGavB+zEw5tRA/dFAqKIocVSs/8GlN6zOAnanwzVA0tjBwltCfE ea/8q+6zGryhPUTI4OYP/M1h1JWxA/cfxs0FdcERt+mCAuqsizOTyGdRNhgIaQo/eAQ8 BKgqED3Du1aqrpbVPMeMdtt06aLhBuuP7QHjzFSp2nccx4KHdo8kcHoXUvPZO6Wmwxa3 L9IEx5rNk7dDZcDUR/ADBmLXRV4wJLnKgs0Iq5TZyrccypyMN8pZduy2sXVy5sRe1nqv yXwA== X-Gm-Message-State: AG10YORVT5LSbO2mYI0BFC5+Sni6nrZb1bb/ni8kB9tK1ck38rm6aU2syCv8fh9/zpgNfA== X-Received: by 10.98.76.19 with SMTP id z19mr11471284pfa.78.1455814467890; Thu, 18 Feb 2016 08:54:27 -0800 (PST) Received: from [127.0.0.1] (mail.questertangent.com. [184.69.10.202]) by smtp.gmail.com with ESMTPSA id xv2sm11552539pab.10.2016.02.18.08.54.26 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 18 Feb 2016 08:54:27 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160218165425.4382803.23287.3091@gmail.com> Date: Thu, 18 Feb 2016 08:54:25 -0800 Subject: Re: Checking FreeBSD kernel with static analyzer From: Russell Haley <russ.haley@gmail.com> To: Warren Block <wblock@wonkity.com>, Svyatoslav Razmyslov <razmyslov@viva64.com> Cc: Fehmi Noyan ISI <fnoyanisi@yahoo.com>, Andrey Karpov <karpov@viva64.com>, freebsd-doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>; List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 18 Feb 2016 16:54:28 -0000 Okay, are those false positives being documented somehow for future referen= ce? If you don't have a bug report nobody knows next time the analyzer is r= un. Or worse an hack like me is looking at the code! even a code comment mi= ght be a good idea about why it's okay? Not releasing the bug list immediately was a wise decision IMHO.=20 Svyatoslav, Is your pre-processor harness open or closed source?=E2=80=8E Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Koodo=C2=A0network. =C2=A0 Original Message =C2=A0 From: Warren Block Sent: Thursday, February 18, 2016 6:47 AM To: Svyatoslav Razmyslov Cc: Russell Haley; Fehmi Noyan ISI; Andrey Karpov; freebsd-doc@FreeBSD.org Subject: Re: Checking FreeBSD kernel with static analyzer On Thu, 18 Feb 2016, Svyatoslav Razmyslov wrote: > I have sent the file in CSV format (PVS-Studio-log-freebsd.csv). Does it = work=20 > for you? > > 18.02.2016 11:24, Russell Haley =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Svyatoslav, >>=20 >> Is there an output format for the issue report that could be massaged in=20 >> python or lua or the like and submitted or imported through bugzilla? CS= V,=20 >> xml, json? The mailing list stripped the attachment, although the mail direct to me=20 included it. The review has been of the text file. We can make the CSV=20 available. Automated creation of bug reports from these results might not be too=20 useful. Many are only suspected problems and turn out to be false=20 positives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1602180738030.18482>