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: <20160613135335.GC3717@pd.tnic>
Date:	Mon, 13 Jun 2016 15:53:35 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Thorsten Leemhuis <regressions@...mhuis.info>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jonathan Corbet <corbet@....net>
Subject: Re: 4.7-rc3: Reported regressions from 4.7

On Mon, Jun 13, 2016 at 03:53:20PM +0200, Rafael J. Wysocki wrote:
> I used kernel BZ entries for two reasons.
> 
> First, some of the bugs were in the kernel BZ already, so they could be added
> to the tracked list very easily when it was in BZ itself.  Second, some people
> actually used BZ entries created by me to work on the bugs going forward (for
> storing logs, acpidumps and similar).

Could be useful too, especially if we mark all entries with some keyword
like "regression" or somesuch and then search for it to geget all
regressions.

@Thorsten: well, if you do use bugzilla, you have everything there and
ready to use :)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ