linux-kernel - Re: [PATCH v2] x86: mtrr: don't modify RdDram/WrDram bits of fixed MTRRs

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]

Date:	Fri, 13 Mar 2009 10:18:12 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Renninger <trenn@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Andreas Herrmann <andreas.herrmann3@....com>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Yinghai Lu <yinghai@...nel.org>,
	Greg Kroah-Hartman <gregkh@...ell.com>
Subject: Re: [PATCH v2] x86: mtrr: don't modify RdDram/WrDram bits of fixed
	MTRRs


* Thomas Renninger <trenn@...e.de> wrote:

> On Friday 13 March 2009 02:58:56 Ingo Molnar wrote:
> > 
> > * Andreas Herrmann <andreas.herrmann3@....com> wrote:
> > 
> > > Impact: bug fix + BIOS workaround
> > 
> > > Change to previous version:
> > > I slightly modified the log message (e.g. addition of FW_WARN).
> > > 
> > > Please consider to apply this patch for .29.
> > 
> > i've applied it to tip:x86/mtrr, thanks Andreas.
> > 
> > I've add a -stable backport tag - so if it's problem-free it 
> > should show up in .29.1.
> 
> What does -stable backport tag mean?

It means such lines added to commit logs:

    Cc: <stable@...nel.org>

Greg has scripting in place to pick up such commits 
automatically into -stable.

AFAIK Andrew Morton was the first maintainer who started using 
these tags consistently, at around 2006.

> Is this something tip:x86 or Ingo Molnar specific?

We do it consistently for all fixes we identify as -stable 
backport candidates that go via -tip but the practice existed 
upstream long before we started doing it.

Even with such tags it's still a lot of non-trivial work to keep 
-stable going:

 - there are those fixes which are identified as fixes only 
   after they have been committed (without tags)

 - there are those fixes that have not been tagged at all

 - often patches will not apply or break if applied out of 
   sequence.

But adding <stable@...nel.org> certainly helps.

> I saw quite some "easy" fixes not being added/submitted to 
> stable in other subsystems and doing double work going through 
> them, pick them out and submit them to stable is an 
> unnecessary waste of time and some fixes will slip through.

Pointing out specific examples where the backport was realized 
when the fix was committed but the tag was not added or outright 
lost, and talking to those those maintainers might help. Often 
it's a matter of "Oh, cool, did not know that!" realization.

Interestingly, the second-ever such tag i found in Git history 
was for a fix ... from you:

 commit 59d399d357a7705568f424c6e861ee8657f7f655
 Author: Thomas Renninger <trenn@...e.de>
 Date:   Tue Nov 8 05:27:00 2005 -0500

    [ACPI] Fix Null pointer deref in video/lcd/brightness

    http://bugzilla.kernel.org/show_bug.cgi?id=5571

    Signed-off-by: Thomas Renninger <trenn@...e.de>
    Signed-off-by: Nishanth Aravamudan <nacc@...ibm.com>
    Signed-off-by: Yu Luming <luming.yu@...il.com>
    Cc: <stable@...nel.org>
    Signed-off-by: Andrew Morton <akpm@...l.org>
    Signed-off-by: Len Brown <len.brown@...el.com>

:-)

	Ingo
--
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/