svn commit: r330952 - head/sys/kern

[Kubilay Kocak]

On 15/03/2018 9:56 am, Alan Somers wrote:
> Well, you _would_ be able to, except the public instance has been down for
> 3 weeks :(
> https://scan.coverity.com/


Coverity Scan is back up as of this (17/03) morning (UTC+11).

Anyone with an account should have received the email notification below
with instructions to reset their passwords:

--------
As you may be aware, there recently was an interruption in the
availability of the Coverity Scan service. In February 2018, we
discovered that servers used for the Coverity Scan service were accessed
by an unauthorized third-party. The access appears to have started
earlier in the month. We suspect that the access was to utilize our
computing power for cryptocurrency mining. We have not found evidence
that database files or artifacts uploaded by the open source community
users of the Coverity Scan service were accessed. We retained a
well-known computer forensics company to assist us in our investigation.

We have closed the method of access, and the Coverity Scan service is
again available as a free service to the open source community. The
Coverity Scan service data is backed up frequently, and Coverity Scan
service data will be restored. We regret any inconvenience caused by the
downtime of the Coverity Scan service.

We take our commitment to the Open Source community seriously. To that
end, we are asking that all Coverity Scan users reset their passwords to
regain access to the service. We are continually assessing and improving
our systems and practices in this environment, and will work with the
Coverity Scan Service community in this effort.

Please note that the servers in question were not connected to any other
Synopsys computer networks. This should have no impact on customers of
our commercial products, and this event did not put any Synopsys
corporate data or intellectual property at risk.

<password reset link>

Note: If you previously signed in to Coverity SCAN using Github, you
need not establish a password at this time, but will need to
re-authorize with Github the next time you sign in.


> On Wed, Mar 14, 2018 at 4:46 PM, Conrad Meyer <cem at freebsd.org> wrote:
> 
>> I believe they didn't come from the public FreeBSD Coverity instance,
>> and I don't think ID numbers are portable between instances.  You
>> might be able to look up similar issues in the public instance,
>> though.
>>
>> Best,
>> Conrad
>>
>> On Wed, Mar 14, 2018 at 3:20 PM, Ravi Pokala <rpokala at mac.com> wrote:
>>> -----Original Message-----
>>> From: <owner-src-committers at freebsd.org> on behalf of Conrad Meyer
>> <cem at FreeBSD.org>
>>> Date: 2018-03-14, Wednesday at 15:11
>>> To: <src-committers at freebsd.org>, <svn-src-all at freebsd.org>, <
>> svn-src-head at freebsd.org>
>>> Subject: svn commit: r330952 - head/sys/kern
>>>
>>>> Author: cem
>>>> Date: Wed Mar 14 22:11:45 2018
>>>> New Revision: 330952
>>>> URL: https://svnweb.freebsd.org/changeset/base/330952
>>>>
>>>> Log:
>>>>   vfs_bio.c: Apply cleanups motivated by Coverity analysis
>>>
>>> What's the Coverity ID?
>>>
>>> Thanks,
>>>
>>> Ravi (rpokala@)
>>>
>>>
>>>
>>
>>
> _______________________________________________
> svn-src-head at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/svn-src-head
> To unsubscribe, send any mail to "svn-src-head-unsubscribe at freebsd.org"
>