linux-kernel - RE: [PATCH] kernel: fix mishandling of out of memory in poweroff

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <829BE905228AE14A9AE1A46E6F2E371605542A19B8@VA3DIAXVS891.RED001.local>
Date:	Tue, 10 Jul 2012 14:37:07 -0700
From:	Scan Subscription <scan-subscription@...erity.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] kernel: fix mishandling of out of memory in poweroff

Hi Andew,

The two reports that were sent on 6/28 and 7/6, were sent manually by us, Coverit Scan Admin, project dedicated for Open Source Community.
But going forward (next week), it will be completely automated. 
Based on the suggestions we got from some of the lead Linux Developer, weekly report includes only "Newly" discovered defects from the code change in that week, and will be sent to maintainer and to the community.
There are on an avg. 5-10 new defects in a week, sometime none.

Any one who wants to contact the person for the reports being sent, they can use the details provided at the end of the email that is scan-admin@...erity.com 
However, we are open to suggestions.

Reasons for using generic email
1. It is desgined to be automated, but so far it was manuall.
2. There are group of people behind this email and not just one. So, anyone who is available will respond.
3. Other Open Source community has shown the same interest to generate report on newly discoverd defect every time build is commited to Scan, and we use the same generic email address to subscribe and to send the reoprt to their mailing list, instead of creating separate email for each Open Source project.

Hence, using either scan-admin@...erity.com or scan-subscription@...erity.com would be fine, but better would be to use the one in the email signaure, that is, scan-admin@...erity.com 
We will add "Reported By" in the next report.

However, as I said, we are open to suggestions.

Thanks
Coverity Scan-Admin scan-admin@...erity.com 
Dakshesh Vyas | Technical Manager - SCAN
Coverity | 185 Berry Street | Suite 6500, Lobby 3 | San Francisco, CA  94107 
Office: 415.935.2957 | dvyas@...erity.com
http://scan.coverity.com 

________________________________________
From: Andrew Morton [akpm@...ux-foundation.org]
Sent: Tuesday, July 10, 2012 1:15 PM
To: Alan Cox
Cc: linux-kernel@...r.kernel.org; Scan Subscription
Subject: Re: [PATCH] kernel: fix mishandling of out of memory in poweroff

On Wed, 04 Jul 2012 16:34:51 +0100
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> From: Alan Cox <alan@...ux.intel.com>
>
> Coverity 703573
>
> Signed-off-by: Alan Cox <alan@...ux.intel.com>

It would be nice to have a Reported-by here, but we were only given
"Scan Subscription <scan-subscription@...erity.com>".

Is there some human behind these reports?  If so, can that person's
details please be included?