linux-kernel - Re: 4.7-rc3: Reported regressions from 4.7

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: <e7510361-eefb-8147-94c6-5ac1c490b991@leemhuis.info>
Date:	Mon, 13 Jun 2016 12:59:26 +0200
From:	Thorsten Leemhuis <regressions@...mhuis.info>
To:	Takashi Iwai <tiwai@...e.de>, Borislav Petkov <bp@...en8.de>
Cc:	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

Takashi Iwai wrote on 13.06.2016 10:20:
> On Mon, 13 Jun 2016 10:07:48 +0200,
> Borislav Petkov wrote:
>> On Sun, Jun 12, 2016 at 07:22:17PM +0200, Thorsten Leemhuis wrote:
>> > Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
>> > I'll try to write regression reports for 4.7. Find the first one below.
>> looks good, thanks for volunteering.
> Indeed, it's really appreciated!

thx!

>> So I'm wondering, would it make more sense to have a web page somewhere
>> which carries all those and gets updated when status ot any tracked
>> regression changes?

Yeah, that would be the good approach, but that would take some time and
work to set up.

> Another idea is to use "Keywords" or "Tags" field in each bugzilla
> entry.  Then you can let bugzilla showing up the all such entries.

Which would mean that all regressions need to get an entry in
bugzilla.kernel.org. I'm not sure if that's a wise approach, as some
developers/subsystems don't use it afaics: some use other bug trackers,
others just use mailing lists and might not be too happy if they'd have
to deal with bugzilla.

Obviously I could file tracking bugs in our bugzilla. But I wonder if
that is worth the work; and it could lead to confusion once a regression
reporter puts some crucial information into the tracking bug entry
instead of posting it to the proper place where the developers discuss
the problem.

CU, knurd