linux-kernel - Re: Scheduled removal of SA

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] [day] [month] [year] [list]

Date:	Sat, 12 May 2007 11:12:43 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	bbpetkov@...oo.de
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Scheduled removal of SA_xxx interrupt flags

On Sat, 12 May 2007 20:07:04 +0200 Borislav Petkov <bbpetkov@...oo.de> wrote:

> Hi Andrew,
> 
>    i've been going over the interrupt-handling code and noticed that the SA_xxx
>    interrupt flags are scheduled for removal sometime in 9/2007 with a prior
>    grace period of 6 months for people to fix external stuff. In order to do so,
>    a __deprecated inline function wraps those flags.
>    What puzzles me is that the __deprecated-patches are only in -mm and not in
>    mainline. Is the -mm-testing audience wide enough to cause userspace to fix
>    their apps prior to the SA_xxx removal or am I missing something? I.e,
>    shouldn't tglx's patches hit mainline first?
> 

No, the deprecation is in mainline now

+static inline
+unsigned long __deprecated deprecated_irq_flag(unsigned long flag)
+{
+	return flag;
+}

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