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, 25 Mar 2011 13:41:24 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Len Brown <lenb@...nel.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>, x86@...nel.org,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86 APM: delete Linux kernel APM support


* Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > > Okay, I can delay this way:
> > > 
> > > 2.6.39:
> > > 	feature-removal.txt targets 2.6.42 removal
> > > 	depend on CONFIG_EXPERT
> > > 
> > > 2.6.40, 2.6.41:
> > > 	WARN once on run-time access
> > > 
> > > 2.6.42:
> > > 	remove.
> > 
> > Regardless of removal, i'd suggest a "this code is not supported" kind of 
> > WARN() message to the APM code today, into .39 - to see whether it pops up 
> > anywhere - and mark it for -stable as well.
> > 
> > .42 removal might be too fast, considering the typical release schedule of 
> > Linux distributions. [...]
> 
> Anyway, i'd ack this schedule if you queued up the WARN() today with a -stable 
> tag, on the condition that if we get complaints about that message, we keep APM 
> support.

s/today/for .39

Thanks,

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ