linux-kernel - Re: Who wants to maintain KR list for stable releases? (was Re: nmi

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: <1188234515.2435.243.camel@dhcp193.mvista.com>
Date:	Mon, 27 Aug 2007 10:08:34 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Björn Steinbrink <B.Steinbrink@....de>,
	eranian@....hp.com, ak@...e.de, linux-kernel@...r.kernel.org,
	Natalie Protasevich <protasnb@...il.com>
Subject: Re: Who wants to maintain KR list for stable releases? (was Re:
	nmi_watchdog=2 regression in 2.6.21)

On Mon, 2007-08-27 at 09:44 -0700, Andrew Morton wrote:

> It's a hassle when someone doesn't have a bugzilla account.  But there are
> humans sitting behind bugzilla handling stuff (fsvo "human").  I've already
> forwarded your bugzilla report to Stephane pointing out that he doesn't
> have an account.
> 
> I screen 100% of new bugzilla reports and for those which I think need
> attention (most), I will ensure that the appropriate parties get to see the
> report.  I'll also verify that the "regression" state is correct and that
> the provided info is sufficient-looking.  (It's amazing how many people
> have trouble with the "Most recent kernel where this bug did not occur:"
> question).

When I read that question, it sort of feels like a mind bender. It's the
"did not occur" , most people are thinking "which version of the kernel
did I find this in", but it's asking the opposite ..

For bug #8945 I really don't recall the version of the kernel I ran when
it worked .. I had to do a bisect to get some clue about that ..
nmi_watchdog isn't something I use every time I boot (I should tho), and
I go through lots of kernels ..

> What I haven't been doing is ensuring that the Product and Component fields
> are suitably set.  That's something which Natalie is now cleaning up.

In terms of regressions, it would be nice for the "Version" field to be
the kernel where the regression first showed up .. Like on bug #8945 I
put in 2.6.22 even tho I found the issue in 2.6.23-rc1 .. Is that
typically what the "Version" field is used for?

Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/